Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 241c3b5f4f89e021198ab619f59286de1ad6e729dbec5a8ac9688062637934fd

Tx prefix hash: dbded38a7dc33fbfd9e2498c507dafd8fd680a7eb4c54a6d78eeff43ee4581f6
Tx public key: 93224694e8de91847e992c4a24ab79a7a7767093ff009be5e2a28e23f7235e33
Timestamp: 1702226226 Timestamp [UCT]: 2023-12-10 16:37:06 Age [y:d:h:m:s]: 01:036:23:28:09
Block: 910196 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287787 RingCT/type: yes/0
Extra: 0193224694e8de91847e992c4a24ab79a7a7767093ff009be5e2a28e23f7235e33021100000005faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67ae41083421ae82e274b0d24026e0a9e14b3e7013642b80fd5ac65309752557 0.600000000000 1367341 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": 910206, "vin": [ { "gen": { "height": 910196 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67ae41083421ae82e274b0d24026e0a9e14b3e7013642b80fd5ac65309752557" } } ], "extra": [ 1, 147, 34, 70, 148, 232, 222, 145, 132, 126, 153, 44, 74, 36, 171, 121, 167, 167, 118, 112, 147, 255, 0, 155, 229, 226, 162, 142, 35, 247, 35, 94, 51, 2, 17, 0, 0, 0, 5, 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