Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70dc80054fb8d59f30681aa4277ea91c77a4aee9451751e0e1327dcc686702d9

Tx prefix hash: fdb458f6c88f281d828e7d6a66a5e00698e20ce4027c35b3a0442092024efa1c
Tx public key: 0bd1e33aca8e34398c76597a8b56095f742849d15bb5a223a0acb6aac3734273
Timestamp: 1577658845 Timestamp [UCT]: 2019-12-29 22:34:05 Age [y:d:h:m:s]: 04:332:13:00:14
Block: 34583 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1126789 RingCT/type: yes/0
Extra: 010bd1e33aca8e34398c76597a8b56095f742849d15bb5a223a0acb6aac373427302110000000f4ac5aa02000000000000000000

1 output(s) for total of 471.425445860000 dcy

stealth address amount amount idx
00: 226631bbe1e7ae5b2efe849a97d98256f09991ef08335a6e05d474fadd37a7cd 471.425445860000 58233 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": 34593, "vin": [ { "gen": { "height": 34583 } } ], "vout": [ { "amount": 471425445860, "target": { "key": "226631bbe1e7ae5b2efe849a97d98256f09991ef08335a6e05d474fadd37a7cd" } } ], "extra": [ 1, 11, 209, 227, 58, 202, 142, 52, 57, 140, 118, 89, 122, 139, 86, 9, 95, 116, 40, 73, 209, 91, 181, 162, 35, 160, 172, 182, 170, 195, 115, 66, 115, 2, 17, 0, 0, 0, 15, 74, 197, 170, 2, 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