Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3bfa99e1b0b7c5071002ac74bebd7baf7a8be1748fa9cf4d48a913240fca6555

Tx prefix hash: a3562183115ae8fad683d02d20a2c2bd4bc983c660e2c4cc255daea9e2c994c2
Tx public key: 0cd1c817d269aa3b4f9f5507c69751bbebff66174d969723d781dfb3050181b7
Timestamp: 1703970166 Timestamp [UCT]: 2023-12-30 21:02:46 Age [y:d:h:m:s]: 01:136:12:39:13
Block: 924647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358721 RingCT/type: yes/0
Extra: 010cd1c817d269aa3b4f9f5507c69751bbebff66174d969723d781dfb3050181b70211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 890855a7030e853837025ed5092f341d7d10c974d76a83149cc27ee5cf56bfdc 0.600000000000 1382403 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": 924657, "vin": [ { "gen": { "height": 924647 } } ], "vout": [ { "amount": 600000000, "target": { "key": "890855a7030e853837025ed5092f341d7d10c974d76a83149cc27ee5cf56bfdc" } } ], "extra": [ 1, 12, 209, 200, 23, 210, 105, 170, 59, 79, 159, 85, 7, 198, 151, 81, 187, 235, 255, 102, 23, 77, 150, 151, 35, 215, 129, 223, 179, 5, 1, 129, 183, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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