Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bae6155da69db0d659b86cd22998152fa2ecae8bb1e0411bbdf26a5d01c220d7

Tx prefix hash: 65cb96cb0a86bc9585e242fdb243ff1c0ca15f38fb8ee15ac01dad791dd70598
Tx public key: 57de2c89cecc14d6c3a4902928d31809446e501623ffda734c4986a4dc968a8e
Timestamp: 1696903185 Timestamp [UCT]: 2023-10-10 01:59:45 Age [y:d:h:m:s]: 01:090:14:35:11
Block: 866280 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326008 RingCT/type: yes/0
Extra: 0157de2c89cecc14d6c3a4902928d31809446e501623ffda734c4986a4dc968a8e021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.827284301000 dcy

stealth address amount amount idx
00: 4841df70cf45469dc8657f033eb09d5c1a2560c83eb56a167854ea0ea46193ed 0.827284301000 1320860 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": 866290, "vin": [ { "gen": { "height": 866280 } } ], "vout": [ { "amount": 827284301, "target": { "key": "4841df70cf45469dc8657f033eb09d5c1a2560c83eb56a167854ea0ea46193ed" } } ], "extra": [ 1, 87, 222, 44, 137, 206, 204, 20, 214, 195, 164, 144, 41, 40, 211, 24, 9, 68, 110, 80, 22, 35, 255, 218, 115, 76, 73, 134, 164, 220, 150, 138, 142, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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