Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3bcee6477a126be60e5d0a55796d1d1a6aa64ef064745b53c8814798be1f3355

Tx prefix hash: f9dc96d581fd58e4751136a72bbcef92d6b5444536f3879bd802e43952fc4ea4
Tx public key: cd461ed66505c812349fd01cd4b4d4db4b83b046a98266e4a5408709463de0b6
Timestamp: 1703057227 Timestamp [UCT]: 2023-12-20 07:27:07 Age [y:d:h:m:s]: 01:110:06:03:58
Block: 917090 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339916 RingCT/type: yes/0
Extra: 01cd461ed66505c812349fd01cd4b4d4db4b83b046a98266e4a5408709463de0b6021100000003e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ead5aecc45833455db31e5cd96b422cca1234e4e3e13c639adf53808c0e29aa7 0.600000000000 1374654 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": 917100, "vin": [ { "gen": { "height": 917090 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ead5aecc45833455db31e5cd96b422cca1234e4e3e13c639adf53808c0e29aa7" } } ], "extra": [ 1, 205, 70, 30, 214, 101, 5, 200, 18, 52, 159, 208, 28, 212, 180, 212, 219, 75, 131, 176, 70, 169, 130, 102, 228, 165, 64, 135, 9, 70, 61, 224, 182, 2, 17, 0, 0, 0, 3, 228, 187, 107, 131, 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