Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84cf9c3e656d6622c4f23501f55e6ebd271c7246867efd1670b8d4576ded8263

Tx prefix hash: 2bf2c227d559c742f938fedee5f7b8fa4cd1458b71bdcb5bb4d1450045e42ef0
Tx public key: d90ffe70c21f847e3293e5939e29491cd3e97c87c072a1ff5dc9c1273ddaf333
Timestamp: 1682591130 Timestamp [UCT]: 2023-04-27 10:25:30 Age [y:d:h:m:s]: 01:265:14:22:50
Block: 747666 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 451296 RingCT/type: yes/0
Extra: 01d90ffe70c21f847e3293e5939e29491cd3e97c87c072a1ff5dc9c1273ddaf333021100000003b3164c24000000000000000000

1 output(s) for total of 2.044901425000 dcy

stealth address amount amount idx
00: a3564cba5961ed3bd06cf4d84481c7b652614cd56ea81bbd0a3d335e8a9ef33e 2.044901425000 1195393 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": 747676, "vin": [ { "gen": { "height": 747666 } } ], "vout": [ { "amount": 2044901425, "target": { "key": "a3564cba5961ed3bd06cf4d84481c7b652614cd56ea81bbd0a3d335e8a9ef33e" } } ], "extra": [ 1, 217, 15, 254, 112, 194, 31, 132, 126, 50, 147, 229, 147, 158, 41, 73, 28, 211, 233, 124, 135, 192, 114, 161, 255, 93, 201, 193, 39, 61, 218, 243, 51, 2, 17, 0, 0, 0, 3, 179, 22, 76, 36, 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