Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b6a2e490f06c7186a2e7cd3355d10f587897e73a3ed831ccd668e2c2f7e2299

Tx prefix hash: a9e372ac6a4e0c1ad8e27675df9e8a751d2884c4260ec301abf594b82469a599
Tx public key: e5497d3dc8cf77424136e8dfc0bab06eb6dca7e07ec8c255a4c89ceeedc8ce25
Timestamp: 1738077004 Timestamp [UCT]: 2025-01-28 15:10:04 Age [y:d:h:m:s]: 00:044:21:28:05
Block: 1207016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32116 RingCT/type: yes/0
Extra: 01e5497d3dc8cf77424136e8dfc0bab06eb6dca7e07ec8c255a4c89ceeedc8ce25021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3f334b0ef3777ca1fc0ad5ec130e25dae79147bb2f708d5db2622e204ea6d84 0.600000000000 1693737 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": 1207026, "vin": [ { "gen": { "height": 1207016 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3f334b0ef3777ca1fc0ad5ec130e25dae79147bb2f708d5db2622e204ea6d84" } } ], "extra": [ 1, 229, 73, 125, 61, 200, 207, 119, 66, 65, 54, 232, 223, 192, 186, 176, 110, 182, 220, 167, 224, 126, 200, 194, 85, 164, 200, 156, 238, 237, 200, 206, 37, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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