Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18e0d8df82403549e447a3ecd861ac51b5b2fa6de0df3d7eff46c299a6b15d36

Tx prefix hash: 297295bc390d603ab8dbb74cdd15146a3d4810794af1ebdaffca108b4327e74a
Tx public key: 75f9d2dcb4ca20e98cc428a63e7aad5be6c8834ee9c7ff4c79292a33d40d49f7
Timestamp: 1608765198 Timestamp [UCT]: 2020-12-23 23:13:18 Age [y:d:h:m:s]: 03:343:21:05:56
Block: 168083 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 997859 RingCT/type: yes/0
Extra: 0175f9d2dcb4ca20e98cc428a63e7aad5be6c8834ee9c7ff4c79292a33d40d49f702110000016baad74b3a000000000000000000

1 output(s) for total of 170.249929294000 dcy

stealth address amount amount idx
00: 5e5e30df382ef82d979492f43ae850dbb3d5bbf42b14b4de616736a44d8e0ab2 170.249929294000 311276 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": 168093, "vin": [ { "gen": { "height": 168083 } } ], "vout": [ { "amount": 170249929294, "target": { "key": "5e5e30df382ef82d979492f43ae850dbb3d5bbf42b14b4de616736a44d8e0ab2" } } ], "extra": [ 1, 117, 249, 210, 220, 180, 202, 32, 233, 140, 196, 40, 166, 62, 122, 173, 91, 230, 200, 131, 78, 233, 199, 255, 76, 121, 41, 42, 51, 212, 13, 73, 247, 2, 17, 0, 0, 1, 107, 170, 215, 75, 58, 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