Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3700c10bfab1e086c621654709f2a65b5748740435fea64a2f99db083f38d95b

Tx prefix hash: 719756122cf4d65433efe8128e6a18320aa30bbc2451012d05fbc1507ff6917e
Tx public key: 3df88e497b7390fa1cdfdf05224b3c1f3b8ce4e907ca8f3311860f88daad2418
Timestamp: 1732649110 Timestamp [UCT]: 2024-11-26 19:25:10 Age [y:d:h:m:s]: 00:135:13:18:07
Block: 1162325 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96696 RingCT/type: yes/0
Extra: 013df88e497b7390fa1cdfdf05224b3c1f3b8ce4e907ca8f3311860f88daad24180211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67e54bffb90eaee7e085ed1ee8c2727b6424d2c143e5f2bcd1c41482552de515 0.600000000000 1647980 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": 1162335, "vin": [ { "gen": { "height": 1162325 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67e54bffb90eaee7e085ed1ee8c2727b6424d2c143e5f2bcd1c41482552de515" } } ], "extra": [ 1, 61, 248, 142, 73, 123, 115, 144, 250, 28, 223, 223, 5, 34, 75, 60, 31, 59, 140, 228, 233, 7, 202, 143, 51, 17, 134, 15, 136, 218, 173, 36, 24, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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