Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f17ff7548cd4113d53c9b04c81043526186f7ce93a85a914a733a6cd2316872a

Tx prefix hash: 47b299789cf96665b5dbff0bd45e0f65ed0844a307b7ab34853ab5b8e8fc48cf
Tx public key: ee5ffb2d897cc1a21dc394c8f007396f5523da12d9675eee7fed6987f0caf8c3
Timestamp: 1713995267 Timestamp [UCT]: 2024-04-24 21:47:47 Age [y:d:h:m:s]: 01:283:16:20:54
Block: 1007777 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 461321 RingCT/type: yes/0
Extra: 01ee5ffb2d897cc1a21dc394c8f007396f5523da12d9675eee7fed6987f0caf8c30211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d9f701aa9fe203ab208a0658dfe33512fba1402c6502475b5a559253495e1b4 0.600000000000 1469221 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": 1007787, "vin": [ { "gen": { "height": 1007777 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d9f701aa9fe203ab208a0658dfe33512fba1402c6502475b5a559253495e1b4" } } ], "extra": [ 1, 238, 95, 251, 45, 137, 124, 193, 162, 29, 195, 148, 200, 240, 7, 57, 111, 85, 35, 218, 18, 217, 103, 94, 238, 127, 237, 105, 135, 240, 202, 248, 195, 2, 17, 0, 0, 0, 3, 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