Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b75d6815dddb1b197d1638d8a74b6c6dc90a453a2add6379efbe0fe50ed258a8

Tx prefix hash: ef894212ab620737a2b1c2605aefcc491f81314b3c2ba7d6104cb5922ade173e
Tx public key: 1b0d4286fbe29bc8b55609e07ebd6de6881723acbb854ee7e2ca0fadf4762e89
Timestamp: 1577711729 Timestamp [UCT]: 2019-12-30 13:15:29 Age [y:d:h:m:s]: 05:065:16:52:30
Block: 35045 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1196710 RingCT/type: yes/0
Extra: 011b0d4286fbe29bc8b55609e07ebd6de6881723acbb854ee7e2ca0fadf4762e890211000000044943cd9f000000000000000000

1 output(s) for total of 469.766693506000 dcy

stealth address amount amount idx
00: 1aabf75004b59d49344458e9e632308697a73b627f51187984bf3ac3cc43a51b 469.766693506000 59038 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": 35055, "vin": [ { "gen": { "height": 35045 } } ], "vout": [ { "amount": 469766693506, "target": { "key": "1aabf75004b59d49344458e9e632308697a73b627f51187984bf3ac3cc43a51b" } } ], "extra": [ 1, 27, 13, 66, 134, 251, 226, 155, 200, 181, 86, 9, 224, 126, 189, 109, 230, 136, 23, 35, 172, 187, 133, 78, 231, 226, 202, 15, 173, 244, 118, 46, 137, 2, 17, 0, 0, 0, 4, 73, 67, 205, 159, 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