Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b341313a562913dc0437a37e94d6c38cf1b2716a835e1c4c5def449ef431289

Tx prefix hash: 12b40876950e3c656e2a69f3ba4f4357bb2d87d13e781e3c75af47729e60b3b0
Tx public key: cf10c3a3946ab71b711025ee91d4d4ed47a21d74da735e4d9ce0e91d80909506
Timestamp: 1755009254 Timestamp [UCT]: 2025-08-12 14:34:14 Age [y:d:h:m:s]: 00:053:04:49:55
Block: 1345513 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37274 RingCT/type: yes/0
Extra: 01cf10c3a3946ab71b711025ee91d4d4ed47a21d74da735e4d9ce0e91d809095060211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 85756b8ab7818ddefdaad2400eb424e499029d70c082e4b88921cbca5e3d1817 0.600000000000 1833406 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": 1345523, "vin": [ { "gen": { "height": 1345513 } } ], "vout": [ { "amount": 600000000, "target": { "key": "85756b8ab7818ddefdaad2400eb424e499029d70c082e4b88921cbca5e3d1817" } } ], "extra": [ 1, 207, 16, 195, 163, 148, 106, 183, 27, 113, 16, 37, 238, 145, 212, 212, 237, 71, 162, 29, 116, 218, 115, 94, 77, 156, 224, 233, 29, 128, 144, 149, 6, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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