Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2995dc5de1ad8e749509325f2420cbde920549457af21f77cb40f7823d0f4fda

Tx prefix hash: 9767416187022e375e8a0c34d4fc007fe0d57fa80dad95b6ba3c8c4ebefb5a92
Tx public key: 6dacb789fd5b109b3f43269f719358059bcd118b54130cddb1f9b424527c993f
Timestamp: 1757691272 Timestamp [UCT]: 2025-09-12 15:34:32 Age [y:d:h:m:s]: 00:100:01:55:37
Block: 1366927 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71661 RingCT/type: yes/0
Extra: 016dacb789fd5b109b3f43269f719358059bcd118b54130cddb1f9b424527c993f021100000003b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a159421167f25bcc42049c5e9fed39c0ec2d3426a5a3a2d4600fb8323e68e03 0.600000000000 1854966 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": 1366937, "vin": [ { "gen": { "height": 1366927 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a159421167f25bcc42049c5e9fed39c0ec2d3426a5a3a2d4600fb8323e68e03" } } ], "extra": [ 1, 109, 172, 183, 137, 253, 91, 16, 155, 63, 67, 38, 159, 113, 147, 88, 5, 155, 205, 17, 139, 84, 19, 12, 221, 177, 249, 180, 36, 82, 124, 153, 63, 2, 17, 0, 0, 0, 3, 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