Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02150422c41e1a1a6ec7f77bda58ea1708069444af03d4148bba4d8dc2ba63ae

Tx prefix hash: 899d55fcd74dea70735ff08ef3b198e62401a7910b47cad50dc0fae914a6aacb
Tx public key: 7722312f5e4eb7e94fac2d0ebaab485a025c85edb38ad5fff68a548c58c22550
Timestamp: 1683803422 Timestamp [UCT]: 2023-05-11 11:10:22 Age [y:d:h:m:s]: 02:011:09:49:16
Block: 757720 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 530295 RingCT/type: yes/0
Extra: 017722312f5e4eb7e94fac2d0ebaab485a025c85edb38ad5fff68a548c58c22550021100000006faf35c9c000000000000000000

1 output(s) for total of 1.893909783000 dcy

stealth address amount amount idx
00: c886562015d43de0218d53b730cbbc33d5e0cb12e5aa9baa353cbd50989a33c9 1.893909783000 1206175 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": 757730, "vin": [ { "gen": { "height": 757720 } } ], "vout": [ { "amount": 1893909783, "target": { "key": "c886562015d43de0218d53b730cbbc33d5e0cb12e5aa9baa353cbd50989a33c9" } } ], "extra": [ 1, 119, 34, 49, 47, 94, 78, 183, 233, 79, 172, 45, 14, 186, 171, 72, 90, 2, 92, 133, 237, 179, 138, 213, 255, 246, 138, 84, 140, 88, 194, 37, 80, 2, 17, 0, 0, 0, 6, 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