Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df7fea8752ed1b70107fb8de4dd77deec791f0a7d4984bf567c88047a91750d9

Tx prefix hash: beada453803eac0a7fd617f734ccca59a23b27b2ac9c1d078c637b04ae669bdf
Tx public key: 3d5c9a9ee91e30f56bada250b2cf4ffcac51533ba39b9ac8ad0812ce516aa4cd
Timestamp: 1746769053 Timestamp [UCT]: 2025-05-09 05:37:33 Age [y:d:h:m:s]: 00:185:18:59:08
Block: 1278946 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130499 RingCT/type: yes/0
Extra: 013d5c9a9ee91e30f56bada250b2cf4ffcac51533ba39b9ac8ad0812ce516aa4cd021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0dc7f6d774d7ff688bda0afbc1ccadc39debaed761fb0fd3f60043cbb15e5c28 0.600000000000 1766317 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": 1278956, "vin": [ { "gen": { "height": 1278946 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0dc7f6d774d7ff688bda0afbc1ccadc39debaed761fb0fd3f60043cbb15e5c28" } } ], "extra": [ 1, 61, 92, 154, 158, 233, 30, 48, 245, 107, 173, 162, 80, 178, 207, 79, 252, 172, 81, 83, 59, 163, 155, 154, 200, 173, 8, 18, 206, 81, 106, 164, 205, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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