Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 268c12c442945677cbd8353b08189beb19f050acac336804b9028269522d3fbc

Tx prefix hash: 39f804c2eeac63392d2726e577949227deb9c9439e3d9fb87f470f5b852e716e
Tx public key: f19d3b96806bb717776abe2afa02fb28a5d4690e4befeaea0adbb4c469fa9c0f
Timestamp: 1734505142 Timestamp [UCT]: 2024-12-18 06:59:02 Age [y:d:h:m:s]: 00:135:16:09:42
Block: 1177728 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96745 RingCT/type: yes/0
Extra: 01f19d3b96806bb717776abe2afa02fb28a5d4690e4befeaea0adbb4c469fa9c0f02110000000139ec141b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b221fac7eae18d3793a4d29388c31ccc0c65e23e17b9e86a8d493ff54db95a0f 0.600000000000 1664105 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": 1177738, "vin": [ { "gen": { "height": 1177728 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b221fac7eae18d3793a4d29388c31ccc0c65e23e17b9e86a8d493ff54db95a0f" } } ], "extra": [ 1, 241, 157, 59, 150, 128, 107, 183, 23, 119, 106, 190, 42, 250, 2, 251, 40, 165, 212, 105, 14, 75, 239, 234, 234, 10, 219, 180, 196, 105, 250, 156, 15, 2, 17, 0, 0, 0, 1, 57, 236, 20, 27, 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