Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: e10591281f40147a52b349a6c5a840c1d8d11ad38bbe9ff891c720c77706a06c

Tx prefix hash: 525a89f5315df2b9c37cb22ad9ba22e93177676a945d00f63c0497f0b33167ee
Tx public key: 78f8948fcd093e2409bbfcb8f59c54f25d15e57bf401f691a1cc182e88b52ccc
Timestamp: 1731996862 Timestamp [UCT]: 2024-11-19 06:14:22 Age [y:d:h:m:s]: 00:169:11:25:45
Block: 1156920 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120958 RingCT/type: yes/0
Extra: 0178f8948fcd093e2409bbfcb8f59c54f25d15e57bf401f691a1cc182e88b52ccc021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49a7e18718ed8ccaeb25c140f59ffe7acd0ff958a2d2baefe7eac69a042edc21 0.600000000000 1642543 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1156930, "vin": [ { "gen": { "height": 1156920 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49a7e18718ed8ccaeb25c140f59ffe7acd0ff958a2d2baefe7eac69a042edc21" } } ], "extra": [ 1, 120, 248, 148, 143, 205, 9, 62, 36, 9, 187, 252, 184, 245, 156, 84, 242, 93, 21, 229, 123, 244, 1, 246, 145, 161, 204, 24, 46, 136, 181, 44, 204, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8