Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 019c163a26db98021e051ecf59173926706f9a0a5b4d3d2c46f590b5da6a44ca

Tx prefix hash: a770025b1092181d48f076cd13b520d9181fcc48d3c1d32b1390d1b75b8e1db6
Tx public key: fd1c8bbff7e4d491159aaba8ad91b3cfc8cd22d9de703d31583cb27633c6699f
Timestamp: 1632390221 Timestamp [UCT]: 2021-09-23 09:43:41 Age [y:d:h:m:s]: 03:168:02:56:50
Block: 339377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 896168 RingCT/type: yes/0
Extra: 01fd1c8bbff7e4d491159aaba8ad91b3cfc8cd22d9de703d31583cb27633c6699f021100000005a272b9cb000000000000000000

1 output(s) for total of 46.079053522000 dcy

stealth address amount amount idx
00: fc7b31fc6e843e20e1a03d5ec0240410bf6c618d1220a902573ebba1bcb20391 46.079053522000 698002 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": 339387, "vin": [ { "gen": { "height": 339377 } } ], "vout": [ { "amount": 46079053522, "target": { "key": "fc7b31fc6e843e20e1a03d5ec0240410bf6c618d1220a902573ebba1bcb20391" } } ], "extra": [ 1, 253, 28, 139, 191, 247, 228, 212, 145, 21, 154, 171, 168, 173, 145, 179, 207, 200, 205, 34, 217, 222, 112, 61, 49, 88, 60, 178, 118, 51, 198, 105, 159, 2, 17, 0, 0, 0, 5, 162, 114, 185, 203, 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