Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd9b4c9d55bd5322aab30139d8960ddcc4597e7a1d04c7cd0872ddd22f0f6988

Tx prefix hash: 67da21cd60b71fa1e1d67cbc7cc5c8b67e08cf88fc938dbe061a5a6784e549ac
Tx public key: a7ee0c6253172959e9d8b93bbc923dc1dc01ea961ff3dc09e2b8dcd536f83b3b
Timestamp: 1577771873 Timestamp [UCT]: 2019-12-31 05:57:53 Age [y:d:h:m:s]: 05:035:06:07:41
Block: 35497 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1174983 RingCT/type: yes/0
Extra: 01a7ee0c6253172959e9d8b93bbc923dc1dc01ea961ff3dc09e2b8dcd536f83b3b0211000000048a2ee0d9000000000000000000

1 output(s) for total of 468.149493366000 dcy

stealth address amount amount idx
00: 66c37666297d8ae3261a1e7d58579d1cecd8917dd2880ef3a157645911b9e170 468.149493366000 59896 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": 35507, "vin": [ { "gen": { "height": 35497 } } ], "vout": [ { "amount": 468149493366, "target": { "key": "66c37666297d8ae3261a1e7d58579d1cecd8917dd2880ef3a157645911b9e170" } } ], "extra": [ 1, 167, 238, 12, 98, 83, 23, 41, 89, 233, 216, 185, 59, 188, 146, 61, 193, 220, 1, 234, 150, 31, 243, 220, 9, 226, 184, 220, 213, 54, 248, 59, 59, 2, 17, 0, 0, 0, 4, 138, 46, 224, 217, 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