Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99883d2bf50a012aad3cd39f072c45b9ff22398ca57c8f9be8778d56248e457d

Tx prefix hash: b6100e1b9d35ec56e1b941c31280c2f5670008535b4fa11b7abce4bf3c52b2cf
Tx public key: 55f496e2192b8ebfa10fb36f0d00f5db979cb55a0789440ecaa7e41770e2a0b1
Timestamp: 1709828345 Timestamp [UCT]: 2024-03-07 16:19:05 Age [y:d:h:m:s]: 01:069:12:50:02
Block: 973230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310705 RingCT/type: yes/0
Extra: 0155f496e2192b8ebfa10fb36f0d00f5db979cb55a0789440ecaa7e41770e2a0b10211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ee220aaf8ae8e13f7cc9275b21810d24c5436f2fa3984593f087c87344e2a75 0.600000000000 1433165 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": 973240, "vin": [ { "gen": { "height": 973230 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ee220aaf8ae8e13f7cc9275b21810d24c5436f2fa3984593f087c87344e2a75" } } ], "extra": [ 1, 85, 244, 150, 226, 25, 43, 142, 191, 161, 15, 179, 111, 13, 0, 245, 219, 151, 156, 181, 90, 7, 137, 68, 14, 202, 167, 228, 23, 112, 226, 160, 177, 2, 17, 0, 0, 0, 7, 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