Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43ba3bc74b41cc63aae07dd3db65febac6d1a59a26ae58edfbf5cf37098118d4

Tx prefix hash: 1babcaa1bd9d886452dd60b1187a95d35bf724516f8c89f94ca5ef6e336d2bb8
Tx public key: ab10a2a25f152efe722adc9d2d5bdbe9011c89ae2a746c6323b2ebf447270c64
Timestamp: 1637768781 Timestamp [UCT]: 2021-11-24 15:46:21 Age [y:d:h:m:s]: 03:074:14:36:55
Block: 381199 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 831971 RingCT/type: yes/0
Extra: 01ab10a2a25f152efe722adc9d2d5bdbe9011c89ae2a746c6323b2ebf447270c64021100000014f6cc1430000000000000000000

1 output(s) for total of 33.491133681000 dcy

stealth address amount amount idx
00: 409e429926d77a4edbd5a68a35b47e33fbc213e4e68e9342a468c79e12b87093 33.491133681000 770167 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": 381209, "vin": [ { "gen": { "height": 381199 } } ], "vout": [ { "amount": 33491133681, "target": { "key": "409e429926d77a4edbd5a68a35b47e33fbc213e4e68e9342a468c79e12b87093" } } ], "extra": [ 1, 171, 16, 162, 162, 95, 21, 46, 254, 114, 42, 220, 157, 45, 91, 219, 233, 1, 28, 137, 174, 42, 116, 108, 99, 35, 178, 235, 244, 71, 39, 12, 100, 2, 17, 0, 0, 0, 20, 246, 204, 20, 48, 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