Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99a7a7db5f28af3636eb2719b173e750df06cee2d2df886d1a36dc5ecfd95921

Tx prefix hash: b2fbf4f16156a06db7e2f863321b0dadc1954fd0c93ab41251c89096dd267f07
Tx public key: 440e06a6db74c7b6159fd9b856ff9c995033e4c0164b95b096e4a26119a3f313
Timestamp: 1725581533 Timestamp [UCT]: 2024-09-06 00:12:13 Age [y:d:h:m:s]: 00:079:07:30:20
Block: 1103835 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56711 RingCT/type: yes/0
Extra: 01440e06a6db74c7b6159fd9b856ff9c995033e4c0164b95b096e4a26119a3f313021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7e2a63092161cd949bd7e3b798eaa3b3c19b461ff14dc6231cb1753ee9b4dce 0.600000000000 1580816 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": 1103845, "vin": [ { "gen": { "height": 1103835 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7e2a63092161cd949bd7e3b798eaa3b3c19b461ff14dc6231cb1753ee9b4dce" } } ], "extra": [ 1, 68, 14, 6, 166, 219, 116, 199, 182, 21, 159, 217, 184, 86, 255, 156, 153, 80, 51, 228, 192, 22, 75, 149, 176, 150, 228, 162, 97, 25, 163, 243, 19, 2, 17, 0, 0, 0, 4, 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