Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7051d2a044e3d86fff4562e817f7bddc517d3a485758d46a3d2554ea103144b

Tx prefix hash: 426419f7107c1c20ea1d7f557656427c93710de0a340f8c71bd03b37a26a46c6
Tx public key: ed0aed6db4ce04355b4342d991c17bb88134a81c0528509a5896e4e0cc005d05
Timestamp: 1697649420 Timestamp [UCT]: 2023-10-18 17:17:00 Age [y:d:h:m:s]: 02:020:22:21:50
Block: 872462 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 534563 RingCT/type: yes/0
Extra: 01ed0aed6db4ce04355b4342d991c17bb88134a81c0528509a5896e4e0cc005d0502110000000275e3f0e9000000000000000000

1 output(s) for total of 0.789171225000 dcy

stealth address amount amount idx
00: ba1b1337e09bf2bfcfa3ad89dd416413eabc7608da8c44c2eff38c992003a020 0.789171225000 1327550 of 0

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": 872472, "vin": [ { "gen": { "height": 872462 } } ], "vout": [ { "amount": 789171225, "target": { "key": "ba1b1337e09bf2bfcfa3ad89dd416413eabc7608da8c44c2eff38c992003a020" } } ], "extra": [ 1, 237, 10, 237, 109, 180, 206, 4, 53, 91, 67, 66, 217, 145, 193, 123, 184, 129, 52, 168, 28, 5, 40, 80, 154, 88, 150, 228, 224, 204, 0, 93, 5, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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