Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a2e368f81a3df37728e06e3e0f2c6590b8514e8a1b778fdd547c6b970411fdc

Tx prefix hash: 4821c17fea411186f8ea7a003b457f5577240e88973a1fbad7657d647e7649e0
Tx public key: fde6c5f5be4afaae51869f59dc37b002b657ae5e1ea05d9296eda6716335fc5b
Timestamp: 1722745655 Timestamp [UCT]: 2024-08-04 04:27:35 Age [y:d:h:m:s]: 01:119:20:40:26
Block: 1080319 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344173 RingCT/type: yes/0
Extra: 01fde6c5f5be4afaae51869f59dc37b002b657ae5e1ea05d9296eda6716335fc5b02110000000d91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf69e10a392c23da093f2715436b6509763160f6c1f1311f0cc65982046da02b 0.600000000000 1553622 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": 1080329, "vin": [ { "gen": { "height": 1080319 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf69e10a392c23da093f2715436b6509763160f6c1f1311f0cc65982046da02b" } } ], "extra": [ 1, 253, 230, 197, 245, 190, 74, 250, 174, 81, 134, 159, 89, 220, 55, 176, 2, 182, 87, 174, 94, 30, 160, 93, 146, 150, 237, 166, 113, 99, 53, 252, 91, 2, 17, 0, 0, 0, 13, 145, 225, 60, 4, 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