Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5cc0c86237152c6a68f6668d030e67b0560709a10e2555aa685d80827e94706

Tx prefix hash: ef6f41af6aa5e1672a75a866b551390dc4af9315deac728df564038f96fa34d9
Tx public key: de8c88ea60e83bc2b12fccec618de88efbd7c7b3171f53308beac165a04482da
Timestamp: 1583637308 Timestamp [UCT]: 2020-03-08 03:15:08 Age [y:d:h:m:s]: 05:041:16:07:46
Block: 78428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1185188 RingCT/type: yes/0
Extra: 01de8c88ea60e83bc2b12fccec618de88efbd7c7b3171f53308beac165a04482da02110000000b8e602c4c000000000000000000

1 output(s) for total of 337.393157968000 dcy

stealth address amount amount idx
00: 3b67338dc331b8836cf39f81d8a0ca50c4594da7b1ff7682359db47a7d9ac747 337.393157968000 143882 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": 78438, "vin": [ { "gen": { "height": 78428 } } ], "vout": [ { "amount": 337393157968, "target": { "key": "3b67338dc331b8836cf39f81d8a0ca50c4594da7b1ff7682359db47a7d9ac747" } } ], "extra": [ 1, 222, 140, 136, 234, 96, 232, 59, 194, 177, 47, 204, 236, 97, 141, 232, 142, 251, 215, 199, 179, 23, 31, 83, 48, 139, 234, 193, 101, 160, 68, 130, 218, 2, 17, 0, 0, 0, 11, 142, 96, 44, 76, 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