Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1544b2ff42f52913a9151933f520ae4779bb240efb4141de78d22204b264cfa0

Tx prefix hash: d8173322925fa37ab910e4a7e1172099589468774f952c9a3b6d991b4a715df6
Tx public key: 34e2cf3cf689140f988a1291d1b7ffa81cbfa0a1b16abe9a3bdd6b3fce9fd6b7
Timestamp: 1720554409 Timestamp [UCT]: 2024-07-09 19:46:49 Age [y:d:h:m:s]: 00:106:20:36:28
Block: 1062153 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76500 RingCT/type: yes/0
Extra: 0134e2cf3cf689140f988a1291d1b7ffa81cbfa0a1b16abe9a3bdd6b3fce9fd6b702110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d910fb90ae21354b120912177997810cc2b954d5e16780b4a0c13766d45663db 0.600000000000 1532654 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": 1062163, "vin": [ { "gen": { "height": 1062153 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d910fb90ae21354b120912177997810cc2b954d5e16780b4a0c13766d45663db" } } ], "extra": [ 1, 52, 226, 207, 60, 246, 137, 20, 15, 152, 138, 18, 145, 209, 183, 255, 168, 28, 191, 160, 161, 177, 106, 190, 154, 59, 221, 107, 63, 206, 159, 214, 183, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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