Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69746953d6cd4e6b44e9e680f7b00016e796a969948a2df3eecbe9543c20777a

Tx prefix hash: 6fb45334c78cc17e2c11bd1af41f154bc516dc045b840a7cd93fb85d9f849db7
Tx public key: 91647107f90983425ad68e892efa3f66754263d46dc16efeac083a00c1b3764f
Timestamp: 1737429945 Timestamp [UCT]: 2025-01-21 03:25:45 Age [y:d:h:m:s]: 00:148:13:20:02
Block: 1201866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105912 RingCT/type: yes/0
Extra: 0191647107f90983425ad68e892efa3f66754263d46dc16efeac083a00c1b3764f02110000000c007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e338d83a59beadd6bbd59c9e15affcb08a40e9b49f4f8de41620c944e23e01f5 0.600000000000 1688523 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": 1201876, "vin": [ { "gen": { "height": 1201866 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e338d83a59beadd6bbd59c9e15affcb08a40e9b49f4f8de41620c944e23e01f5" } } ], "extra": [ 1, 145, 100, 113, 7, 249, 9, 131, 66, 90, 214, 142, 137, 46, 250, 63, 102, 117, 66, 99, 212, 109, 193, 110, 254, 172, 8, 58, 0, 193, 179, 118, 79, 2, 17, 0, 0, 0, 12, 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