Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16d5556b75395eb0efd9758f30ab427b9588e2acf4b6d245676fe1d3ed96fa79

Tx prefix hash: 247253ab22e4dc8ea55ddb8a450f3ab585796c4ad5c3642fac785cc5c9be3f51
Tx public key: 3e426a80280747c5616c68a35c65ad9d8905ef6db8ae921194a3a59a4808b14d
Timestamp: 1736729496 Timestamp [UCT]: 2025-01-13 00:51:36 Age [y:d:h:m:s]: 00:159:01:01:56
Block: 1196104 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113331 RingCT/type: yes/0
Extra: 013e426a80280747c5616c68a35c65ad9d8905ef6db8ae921194a3a59a4808b14d021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad8a8d5534c3d6a7e1af865aea70a3da456683589c4cf8d640b8cbbaccfb3dc9 0.600000000000 1682701 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": 1196114, "vin": [ { "gen": { "height": 1196104 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad8a8d5534c3d6a7e1af865aea70a3da456683589c4cf8d640b8cbbaccfb3dc9" } } ], "extra": [ 1, 62, 66, 106, 128, 40, 7, 71, 197, 97, 108, 104, 163, 92, 101, 173, 157, 137, 5, 239, 109, 184, 174, 146, 17, 148, 163, 165, 154, 72, 8, 177, 77, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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