Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 239d471909bcf542d382b5982de807e33390869c93aedf02a43e9efc2aa2c807

Tx prefix hash: 1d3c5f8f699bbd7679f676e83de456cf0f3754a0afa9a3b8939a688c118eaa1e
Tx public key: 5b46622f327313b9db80b79cb86d7a34e2ac64afee20aedae7ef2a8c3de54b36
Timestamp: 1583894846 Timestamp [UCT]: 2020-03-11 02:47:26 Age [y:d:h:m:s]: 04:240:06:40:28
Block: 80239 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1066757 RingCT/type: yes/0
Extra: 015b46622f327313b9db80b79cb86d7a34e2ac64afee20aedae7ef2a8c3de54b36021100000001c48ea382000000000000000000

1 output(s) for total of 332.771072532000 dcy

stealth address amount amount idx
00: 9e94a82166b03df0f705f0226d60313e72d4a15ef8a43360d84ff329c70003dc 332.771072532000 146835 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": 80249, "vin": [ { "gen": { "height": 80239 } } ], "vout": [ { "amount": 332771072532, "target": { "key": "9e94a82166b03df0f705f0226d60313e72d4a15ef8a43360d84ff329c70003dc" } } ], "extra": [ 1, 91, 70, 98, 47, 50, 115, 19, 185, 219, 128, 183, 156, 184, 109, 122, 52, 226, 172, 100, 175, 238, 32, 174, 218, 231, 239, 42, 140, 61, 229, 75, 54, 2, 17, 0, 0, 0, 1, 196, 142, 163, 130, 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