Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 785d43dd43d55dc4f56172dc5e3c3fc1eedce095082ffbf6d79c0e0eb28809ee

Tx prefix hash: 1ef6369dd49282247fcca599756af03c529fe9aed7eb844b7a31fbe05bde4969
Tx public key: 5d26f73de4cde18d44987d5ceb90d34ce39a9575016df9e09f5c3e6a1a14b40c
Timestamp: 1754217120 Timestamp [UCT]: 2025-08-03 10:32:00 Age [y:d:h:m:s]: 00:016:09:29:48
Block: 1339362 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10725 RingCT/type: yes/0
Extra: 015d26f73de4cde18d44987d5ceb90d34ce39a9575016df9e09f5c3e6a1a14b40c0211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4c684bed47acf0080fc0cece1d5b7ab7509d3ef87484f0601c489c0d7e7b74a 0.600000000000 1827175 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": 1339372, "vin": [ { "gen": { "height": 1339362 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4c684bed47acf0080fc0cece1d5b7ab7509d3ef87484f0601c489c0d7e7b74a" } } ], "extra": [ 1, 93, 38, 247, 61, 228, 205, 225, 141, 68, 152, 125, 92, 235, 144, 211, 76, 227, 154, 149, 117, 1, 109, 249, 224, 159, 92, 62, 106, 26, 20, 180, 12, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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