Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60402037a73110f0b519f6e53f5e1c9b12b991feec97c6700d29a6aaed372d92

Tx prefix hash: cefc2433ad1836934aa5bad9d7aaa9b2bf4d0ef2a8396c553acb5c754c1117fe
Tx public key: 9dfadcd21cc67c9acb75e51bde3963f84ac2198b3cb2d290ba747ef02d60e002
Timestamp: 1755690904 Timestamp [UCT]: 2025-08-20 11:55:04 Age [y:d:h:m:s]: 00:098:02:10:35
Block: 1350558 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70024 RingCT/type: yes/0
Extra: 019dfadcd21cc67c9acb75e51bde3963f84ac2198b3cb2d290ba747ef02d60e002021100000006b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ace21ec1c42faf0ba7ea5127bd75ea70c2b4f46c14d62eb4a0cd4a769def9572 0.600000000000 1838503 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": 1350568, "vin": [ { "gen": { "height": 1350558 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ace21ec1c42faf0ba7ea5127bd75ea70c2b4f46c14d62eb4a0cd4a769def9572" } } ], "extra": [ 1, 157, 250, 220, 210, 28, 198, 124, 154, 203, 117, 229, 27, 222, 57, 99, 248, 74, 194, 25, 139, 60, 178, 210, 144, 186, 116, 126, 240, 45, 96, 224, 2, 2, 17, 0, 0, 0, 6, 178, 247, 132, 196, 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