Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82242505625b42d106917381ce38aff394fdc7317477568e7721b44b1afc8d4a

Tx prefix hash: 8a9e43b8bfa18d1e0a14cfcdfb254a969ee862ae9f75b67780b49a8060a89671
Tx public key: 372f9d6764d5f0d31c789309463493ac88959b559623af9f85b4a37d4b47e9e4
Timestamp: 1702791608 Timestamp [UCT]: 2023-12-17 05:40:08 Age [y:d:h:m:s]: 01:034:08:30:21
Block: 914890 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285869 RingCT/type: yes/0
Extra: 01372f9d6764d5f0d31c789309463493ac88959b559623af9f85b4a37d4b47e9e4021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b64bd25bc3d66172fd84737c1649c1600c29faf71e200ace3a57ef844c10ea75 0.600000000000 1372242 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": 914900, "vin": [ { "gen": { "height": 914890 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b64bd25bc3d66172fd84737c1649c1600c29faf71e200ace3a57ef844c10ea75" } } ], "extra": [ 1, 55, 47, 157, 103, 100, 213, 240, 211, 28, 120, 147, 9, 70, 52, 147, 172, 136, 149, 155, 85, 150, 35, 175, 159, 133, 180, 163, 125, 75, 71, 233, 228, 2, 17, 0, 0, 0, 7, 230, 210, 127, 156, 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