Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f85eb91a013cbee5e3c62c93e10e789492c4b92df99745228ab02f9b03fdf121

Tx prefix hash: d48992d6a9387ea94bcd1e4c137e1e06bac5a556a2661fc65a0635009770b04e
Tx public key: 0046c5f46460a010be833f115de36a64d99e3f9b1668dc7f47fa37add0620c3c
Timestamp: 1702581429 Timestamp [UCT]: 2023-12-14 19:17:09 Age [y:d:h:m:s]: 01:333:12:16:59
Block: 913142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 497218 RingCT/type: yes/0
Extra: 010046c5f46460a010be833f115de36a64d99e3f9b1668dc7f47fa37add0620c3c02110000000575e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50b2e2a063223bd31009e5d204e88ffe6757106ac63bdb851914b5cb4c1a7362 0.600000000000 1370388 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": 913152, "vin": [ { "gen": { "height": 913142 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50b2e2a063223bd31009e5d204e88ffe6757106ac63bdb851914b5cb4c1a7362" } } ], "extra": [ 1, 0, 70, 197, 244, 100, 96, 160, 16, 190, 131, 63, 17, 93, 227, 106, 100, 217, 158, 63, 155, 22, 104, 220, 127, 71, 250, 55, 173, 208, 98, 12, 60, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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