Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 032e39599e488641344e2f6e77af34d63b2d3f5f176ad776b9b8134aa59d2547

Tx prefix hash: 6128f88547f0e19b91698031602c347e09f7cba47a57f61ed8d3ead95ac670c4
Tx public key: d6b250a09c42b14102d20dfd5d89e1ed17a17d8d8005a0b020990b74ca0c9d77
Timestamp: 1707344878 Timestamp [UCT]: 2024-02-07 22:27:58 Age [y:d:h:m:s]: 01:092:18:39:57
Block: 952636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327376 RingCT/type: yes/0
Extra: 01d6b250a09c42b14102d20dfd5d89e1ed17a17d8d8005a0b020990b74ca0c9d7702110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5edd360f1626928e493f088c07511dd07ad5bfdd0109c21d4a90229721e75c8 0.600000000000 1411722 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": 952646, "vin": [ { "gen": { "height": 952636 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5edd360f1626928e493f088c07511dd07ad5bfdd0109c21d4a90229721e75c8" } } ], "extra": [ 1, 214, 178, 80, 160, 156, 66, 177, 65, 2, 210, 13, 253, 93, 137, 225, 237, 23, 161, 125, 141, 128, 5, 160, 176, 32, 153, 11, 116, 202, 12, 157, 119, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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