Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0dead2b6e4c6b229d4724d4f87863034685f8ad764257bf9d8d88d5a5b153330

Tx prefix hash: 83a5079b295b3ef0bae2a43ddb3113c4693ef4bce8b76daea1b26f92d38c0ad9
Tx public key: e6a85268ed9212aab4f33a7fe0a703033792071904ae01871e7e661fb0e5d492
Timestamp: 1737734961 Timestamp [UCT]: 2025-01-24 16:09:21 Age [y:d:h:m:s]: 00:144:00:33:01
Block: 1204390 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102682 RingCT/type: yes/0
Extra: 01e6a85268ed9212aab4f33a7fe0a703033792071904ae01871e7e661fb0e5d492021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 93706531204cd4b68ca033d2d93ee302d41c7d07bc2363ae66422b7c7537c71c 0.600000000000 1691075 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": 1204400, "vin": [ { "gen": { "height": 1204390 } } ], "vout": [ { "amount": 600000000, "target": { "key": "93706531204cd4b68ca033d2d93ee302d41c7d07bc2363ae66422b7c7537c71c" } } ], "extra": [ 1, 230, 168, 82, 104, 237, 146, 18, 170, 180, 243, 58, 127, 224, 167, 3, 3, 55, 146, 7, 25, 4, 174, 1, 135, 30, 126, 102, 31, 176, 229, 212, 146, 2, 17, 0, 0, 0, 2, 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