Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 297bc093ea15747dac43cb60a291bf466c3dc9f8820f175fdc0b313974c1b5b5

Tx prefix hash: 37b5889d8099bc7a49a9b746087df656bfd755a68ff6c52fdc30e5fed3c95cf3
Tx public key: a25a9bcf0fe3ee20e82b016030a2f1cc424bc9e24d0ef7299bb2cead5b873eb7
Timestamp: 1755050712 Timestamp [UCT]: 2025-08-13 02:05:12 Age [y:d:h:m:s]: 00:053:19:24:43
Block: 1345779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37788 RingCT/type: yes/0
Extra: 01a25a9bcf0fe3ee20e82b016030a2f1cc424bc9e24d0ef7299bb2cead5b873eb70211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51e260d9967826c2a43d08b55d68de11be094a99187c9bfaf8113b94642ddaa8 0.600000000000 1833674 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": 1345789, "vin": [ { "gen": { "height": 1345779 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51e260d9967826c2a43d08b55d68de11be094a99187c9bfaf8113b94642ddaa8" } } ], "extra": [ 1, 162, 90, 155, 207, 15, 227, 238, 32, 232, 43, 1, 96, 48, 162, 241, 204, 66, 75, 201, 226, 77, 14, 247, 41, 155, 178, 206, 173, 91, 135, 62, 183, 2, 17, 0, 0, 0, 2, 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