Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ecf19eede02fd6873923daf2afe201117f2e2e6f462f182be9bcb30c8f2b5c3

Tx prefix hash: 84e294bd03a6bf7878c0d21c0cae47e2b85dab322e20810a3159bbc3788b5ade
Tx public key: 497c994164a243ce4d3911d5283259f91de3f90565fa3b6454ea588fad5c046b
Timestamp: 1727751887 Timestamp [UCT]: 2024-10-01 03:04:47 Age [y:d:h:m:s]: 00:113:16:59:51
Block: 1121823 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81260 RingCT/type: yes/0
Extra: 01497c994164a243ce4d3911d5283259f91de3f90565fa3b6454ea588fad5c046b02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8cfe4c0bf3799f61be0aad3ab8335c8dc3d22b330ac03d5621706f18b1ef5259 0.600000000000 1604176 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": 1121833, "vin": [ { "gen": { "height": 1121823 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8cfe4c0bf3799f61be0aad3ab8335c8dc3d22b330ac03d5621706f18b1ef5259" } } ], "extra": [ 1, 73, 124, 153, 65, 100, 162, 67, 206, 77, 57, 17, 213, 40, 50, 89, 249, 29, 227, 249, 5, 101, 250, 59, 100, 84, 234, 88, 143, 173, 92, 4, 107, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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