Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ae8f8fd83fc1dcddb0c4dda410be83d56cf4841bb80a3cec24500039e43b3e2

Tx prefix hash: 0c639cb855688739f1f30eae2fdeaa7a4c610b38ab24934587dc28b5acd222d3
Tx public key: f1881dda22c0ad54224898ff007dd17804a37b6a1c87458b2c3379e4e52dba20
Timestamp: 1722494941 Timestamp [UCT]: 2024-08-01 06:49:01 Age [y:d:h:m:s]: 00:238:03:41:07
Block: 1078237 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170092 RingCT/type: yes/0
Extra: 01f1881dda22c0ad54224898ff007dd17804a37b6a1c87458b2c3379e4e52dba20021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a648d7d8df7b9be060993b1be0a3b3f77d657d223d0a21c0e67264c0e0cf207 0.600000000000 1550810 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": 1078247, "vin": [ { "gen": { "height": 1078237 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a648d7d8df7b9be060993b1be0a3b3f77d657d223d0a21c0e67264c0e0cf207" } } ], "extra": [ 1, 241, 136, 29, 218, 34, 192, 173, 84, 34, 72, 152, 255, 0, 125, 209, 120, 4, 163, 123, 106, 28, 135, 69, 139, 44, 51, 121, 228, 229, 45, 186, 32, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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