Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7104d54cf80a398572a21522c60de2d9c1d9a79f1a062f5a782a6f9de9a8285

Tx prefix hash: 338c3b6d5b46980df5c10495bb061b3cbd1e705491fe3a2d95dcfb8c17edf468
Tx public key: 9d1b2789b06ab47479e0c659a474d7e10955f02774534064860c9cd579647866
Timestamp: 1708592154 Timestamp [UCT]: 2024-02-22 08:55:54 Age [y:d:h:m:s]: 01:116:02:03:23
Block: 962975 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 343933 RingCT/type: yes/0
Extra: 019d1b2789b06ab47479e0c659a474d7e10955f02774534064860c9cd5796478660211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb03e307a8616281dd2d3fe33ea6a1940e9ef8fc240d207ae6f691f718b16abb 0.600000000000 1422668 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": 962985, "vin": [ { "gen": { "height": 962975 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb03e307a8616281dd2d3fe33ea6a1940e9ef8fc240d207ae6f691f718b16abb" } } ], "extra": [ 1, 157, 27, 39, 137, 176, 106, 180, 116, 121, 224, 198, 89, 164, 116, 215, 225, 9, 85, 240, 39, 116, 83, 64, 100, 134, 12, 156, 213, 121, 100, 120, 102, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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