Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05fa97d5b2e7c7f7e48cdf63546c2a80c8038298a563e9499d5dad9f27cb2a20

Tx prefix hash: e49b4d4db792fb3f2fe9f8c4578281d845942bad3eae61739f928c646a260037
Tx public key: fcfaa54dadadda071095b95914c7014fb9a20b561bb8e8508a0dba186e3c3b74
Timestamp: 1578391918 Timestamp [UTC]: 2020-01-07 10:11:58 Age [y:d:h:m:s]: 06:043:04:35:35
Block: 40393 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1439439 RingCT/type: yes/0
Extra: 01fcfaa54dadadda071095b95914c7014fb9a20b561bb8e8508a0dba186e3c3b740211000000074ac5aa02000000000000000000

1 output(s) for total of 0.450992751830 xmr

stealth address amount amount idx tag
00: 082d5c271352a93d65761799f429114a9cea44af4f507ce59f5024246e9c6c78 0.450992751830 70860 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 dinastycoin-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": 40403, "vin": [ { "gen": { "height": 40393 } } ], "vout": [ { "amount": 450992751830, "target": { "key": "082d5c271352a93d65761799f429114a9cea44af4f507ce59f5024246e9c6c78" } } ], "extra": [ 1, 252, 250, 165, 77, 173, 173, 218, 7, 16, 149, 185, 89, 20, 199, 1, 79, 185, 162, 11, 86, 27, 184, 232, 80, 138, 13, 186, 24, 110, 60, 59, 116, 2, 17, 0, 0, 0, 7, 74, 197, 170, 2, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369