Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 564b229d2b61a8f6d7f227f30ed36b3d014129443b2a78d0bafab6807ed5bc07

Tx prefix hash: 43ded65553f28e5a8fa30552a2601485503f55f47e72b0b81b9bc94a715c1fac
Tx public key: 04f7b6cfed63dd692adb13ca40b62cab76b12e0feff70d8bb8d9696f2a5a657b
Timestamp: 1681773841 Timestamp [UCT]: 2023-04-17 23:24:01 Age [y:d:h:m:s]: 01:312:15:08:31
Block: 740887 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 484668 RingCT/type: yes/0
Extra: 0104f7b6cfed63dd692adb13ca40b62cab76b12e0feff70d8bb8d9696f2a5a657b0211000000045029cbac000000000000000000

1 output(s) for total of 2.153446212000 dcy

stealth address amount amount idx
00: f3c7bc88f501e728ff1f20b42eb1407603833cfec1f583484a9fc64c212f6962 2.153446212000 1187794 of 0

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": 740897, "vin": [ { "gen": { "height": 740887 } } ], "vout": [ { "amount": 2153446212, "target": { "key": "f3c7bc88f501e728ff1f20b42eb1407603833cfec1f583484a9fc64c212f6962" } } ], "extra": [ 1, 4, 247, 182, 207, 237, 99, 221, 105, 42, 219, 19, 202, 64, 182, 44, 171, 118, 177, 46, 15, 239, 247, 13, 139, 184, 217, 105, 111, 42, 90, 101, 123, 2, 17, 0, 0, 0, 4, 80, 41, 203, 172, 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