Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd2923473c18a7f189c5aac7bf579db6e42db5e67aa0450ef26413dd8e28bfb0

Tx prefix hash: 2a400e2b1ec914f9c2ef04bd7e06cf9dd005022ea65676cd0fbefcd70530e22f
Tx public key: b4b872b009313f149800e0d6a7ded11c837d9ca204f069f7411c5a6a597ce8b8
Timestamp: 1641094343 Timestamp [UCT]: 2022-01-02 03:32:23 Age [y:d:h:m:s]: 02:330:08:59:00
Block: 408588 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 754246 RingCT/type: yes/0
Extra: 01b4b872b009313f149800e0d6a7ded11c837d9ca204f069f7411c5a6a597ce8b80211000000240bc544d7000000000000000000

1 output(s) for total of 27.175571241000 dcy

stealth address amount amount idx
00: 40a06f685ac856d275709895244ffb19e656f1971746f9579559d9cfe71a7626 27.175571241000 810713 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": 408598, "vin": [ { "gen": { "height": 408588 } } ], "vout": [ { "amount": 27175571241, "target": { "key": "40a06f685ac856d275709895244ffb19e656f1971746f9579559d9cfe71a7626" } } ], "extra": [ 1, 180, 184, 114, 176, 9, 49, 63, 20, 152, 0, 224, 214, 167, 222, 209, 28, 131, 125, 156, 162, 4, 240, 105, 247, 65, 28, 90, 106, 89, 124, 232, 184, 2, 17, 0, 0, 0, 36, 11, 197, 68, 215, 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