Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad1a61c972dff521e5563a379a71decfa4e696471f9e78fb9392a973d25ae687

Tx prefix hash: 7a688241a5fbb2046df02b8dcd62ca9bb5b9784051abbb9ac3d35e3e9a17b888
Tx public key: 1542b9d54f0019cb320e037a15557c73e229604e47dfce22e816aa699d934b55
Timestamp: 1719360249 Timestamp [UCT]: 2024-06-26 00:04:09 Age [y:d:h:m:s]: 00:265:09:56:55
Block: 1052237 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189670 RingCT/type: yes/0
Extra: 011542b9d54f0019cb320e037a15557c73e229604e47dfce22e816aa699d934b5502110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f855d73092b43aa396289950ec4f504701ff3d4eb63a2c6469a43af298aa5b5 0.600000000000 1522560 of 15

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": 1052247, "vin": [ { "gen": { "height": 1052237 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f855d73092b43aa396289950ec4f504701ff3d4eb63a2c6469a43af298aa5b5" } } ], "extra": [ 1, 21, 66, 185, 213, 79, 0, 25, 203, 50, 14, 3, 122, 21, 85, 124, 115, 226, 41, 96, 78, 71, 223, 206, 34, 232, 22, 170, 105, 157, 147, 75, 85, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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