Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22f586b61c31d8dca324615f0f1e0ca438ede242c8ade5f9fbab841e67882153

Tx prefix hash: ec91155381a79f68e90ab3f2787ca770769e21843c353728341b14f5344b381e
Tx public key: f6b055c1ed2da5161f0e354d112432ac1d87b0d1ca0204c176480b1b35e8b153
Timestamp: 1703870901 Timestamp [UCT]: 2023-12-29 17:28:21 Age [y:d:h:m:s]: 01:316:02:10:57
Block: 923833 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 484750 RingCT/type: yes/0
Extra: 01f6b055c1ed2da5161f0e354d112432ac1d87b0d1ca0204c176480b1b35e8b1530211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32fb7863d7d39dc7b5eb370d0824664c0d82ddb5a8a80b5b8d88feab10d2fbe5 0.600000000000 1381571 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": 923843, "vin": [ { "gen": { "height": 923833 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32fb7863d7d39dc7b5eb370d0824664c0d82ddb5a8a80b5b8d88feab10d2fbe5" } } ], "extra": [ 1, 246, 176, 85, 193, 237, 45, 165, 22, 31, 14, 53, 77, 17, 36, 50, 172, 29, 135, 176, 209, 202, 2, 4, 193, 118, 72, 11, 27, 53, 232, 177, 83, 2, 17, 0, 0, 0, 6, 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