Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d78c87838ab760ef4f718c6260ad29793e6bdf9f92da5af4d9b3f3aa74e3711

Tx prefix hash: 172684817d091a28c43a11136f0e5b09a85ca4ebd6abf73fa83da8997caf99f6
Tx public key: 8ade155ed3b93de54c91d0a40e179ef94fc75351ddd983d4d5636d9ac113f99a
Timestamp: 1706720028 Timestamp [UCT]: 2024-01-31 16:53:48 Age [y:d:h:m:s]: 01:067:13:05:19
Block: 947433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309344 RingCT/type: yes/0
Extra: 018ade155ed3b93de54c91d0a40e179ef94fc75351ddd983d4d5636d9ac113f99a0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 55b2e14a7ad99dffa1d455f0fc3d32e7e78a400ea40d95dfde04b8a253e8848e 0.600000000000 1405781 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": 947443, "vin": [ { "gen": { "height": 947433 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55b2e14a7ad99dffa1d455f0fc3d32e7e78a400ea40d95dfde04b8a253e8848e" } } ], "extra": [ 1, 138, 222, 21, 94, 211, 185, 61, 229, 76, 145, 208, 164, 14, 23, 158, 249, 79, 199, 83, 81, 221, 217, 131, 212, 213, 99, 109, 154, 193, 19, 249, 154, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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