Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 660099d4e8898dc715b0e5786f1c1020d002ba9f149442e697454386f8422f89

Tx prefix hash: be3431fc8081c46f95e286a8d70fab2dfb9a85d4b2df63cc47470ea6427c6019
Tx public key: 3005c8bf632bb34f40154911108dabe4afc7ab5bbc945368cbc23aa0b06bda89
Timestamp: 1712898120 Timestamp [UCT]: 2024-04-12 05:02:00 Age [y:d:h:m:s]: 01:047:04:38:59
Block: 998653 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294750 RingCT/type: yes/0
Extra: 013005c8bf632bb34f40154911108dabe4afc7ab5bbc945368cbc23aa0b06bda890211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f19d5706e29cd936f514cc51a4eef2cc355662bdb5e3dee950c32231c6a1e2f2 0.600000000000 1459105 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": 998663, "vin": [ { "gen": { "height": 998653 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f19d5706e29cd936f514cc51a4eef2cc355662bdb5e3dee950c32231c6a1e2f2" } } ], "extra": [ 1, 48, 5, 200, 191, 99, 43, 179, 79, 64, 21, 73, 17, 16, 141, 171, 228, 175, 199, 171, 91, 188, 148, 83, 104, 203, 194, 58, 160, 176, 107, 218, 137, 2, 17, 0, 0, 0, 2, 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