Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4dd8a49e6b7f73982cdd8603753b2978534346db713636d2b72836c589465f8

Tx prefix hash: adc16b5719159c2b61c932fe9b64d833b2431f1bead6aaa6c162402a52ca9d85
Tx public key: c2b2daf235f9110a1198025ac31a60eb46b9e8fcc5e8e673d97f881e30cc1c33
Timestamp: 1702852317 Timestamp [UCT]: 2023-12-17 22:31:57 Age [y:d:h:m:s]: 01:331:23:35:50
Block: 915393 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 496120 RingCT/type: yes/0
Extra: 01c2b2daf235f9110a1198025ac31a60eb46b9e8fcc5e8e673d97f881e30cc1c33021100000002faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 849511bba51315b8d9932621d5113994b396e47dd29d1a9b75588447815089c5 0.600000000000 1372789 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": 915403, "vin": [ { "gen": { "height": 915393 } } ], "vout": [ { "amount": 600000000, "target": { "key": "849511bba51315b8d9932621d5113994b396e47dd29d1a9b75588447815089c5" } } ], "extra": [ 1, 194, 178, 218, 242, 53, 249, 17, 10, 17, 152, 2, 90, 195, 26, 96, 235, 70, 185, 232, 252, 197, 232, 230, 115, 217, 127, 136, 30, 48, 204, 28, 51, 2, 17, 0, 0, 0, 2, 250, 243, 92, 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