Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4857c42608afb496b9144c05f2d0dfc7ffefefde023808fcde553938e66f302f

Tx prefix hash: bccb37a80ff2ec96d5b5d42f712e57951c699576aabf3271c822fd47b3894e9d
Tx public key: 3f1b0e1d2a5d960e9d84e32f1487c1bfd829952fc397d177c76aad78f599558b
Timestamp: 1707690578 Timestamp [UCT]: 2024-02-11 22:29:38 Age [y:d:h:m:s]: 00:314:21:51:07
Block: 955491 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225497 RingCT/type: yes/0
Extra: 013f1b0e1d2a5d960e9d84e32f1487c1bfd829952fc397d177c76aad78f599558b0211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 919a7d14d5a6183381770de9df7d59ee1051e25daf378f3fcedc8eaeede63753 0.600000000000 1414781 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": 955501, "vin": [ { "gen": { "height": 955491 } } ], "vout": [ { "amount": 600000000, "target": { "key": "919a7d14d5a6183381770de9df7d59ee1051e25daf378f3fcedc8eaeede63753" } } ], "extra": [ 1, 63, 27, 14, 29, 42, 93, 150, 14, 157, 132, 227, 47, 20, 135, 193, 191, 216, 41, 149, 47, 195, 151, 209, 119, 199, 106, 173, 120, 245, 153, 85, 139, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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