Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 431add39762e4d54c3f52aaa2fe348d60df997cda64bcf26e3ffd96d0b2e8bd5

Tx prefix hash: abc79c3c0f0d136bdb456beeb7787f8869f4565530f84dfddcb2a74e868948bc
Tx public key: 686aba1b2f4a614a8dbc1292802057674f8c759a21e59eacb65ac3ca437d7e27
Timestamp: 1762204905 Timestamp [UCT]: 2025-11-03 21:21:45 Age [y:d:h:m:s]: 00:017:03:02:37
Block: 1404329 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12253 RingCT/type: yes/0
Extra: 01686aba1b2f4a614a8dbc1292802057674f8c759a21e59eacb65ac3ca437d7e27021100000002df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c9871aa091af18ac7e0098ab768ef2b42f8e403a7f995990dd6e651e1da5fd18 0.600000000000 1892686 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": 1404339, "vin": [ { "gen": { "height": 1404329 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c9871aa091af18ac7e0098ab768ef2b42f8e403a7f995990dd6e651e1da5fd18" } } ], "extra": [ 1, 104, 106, 186, 27, 47, 74, 97, 74, 141, 188, 18, 146, 128, 32, 87, 103, 79, 140, 117, 154, 33, 229, 158, 172, 182, 90, 195, 202, 67, 125, 126, 39, 2, 17, 0, 0, 0, 2, 223, 90, 36, 122, 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