Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19e9978c3a0cd5d6b88a3667e62c352a10a1075aa4d9a794e33f3e509fbfe727

Tx prefix hash: 0df51a77dba2a552d088ff6e55fefe0180ddb791d75f76326519cbd960e2b79f
Tx public key: fb269ea87a152d271bac405c22b6b47f764b4325ba7608ad7f6afca7bdcb63e0
Timestamp: 1579424017 Timestamp [UTC]: 2020-01-19 08:53:37 Age [y:d:h:m:s]: 06:218:05:39:05
Block: 48702 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1570540 RingCT/type: yes/0
Extra: 01fb269ea87a152d271bac405c22b6b47f764b4325ba7608ad7f6afca7bdcb63e00211000000042264afe6000000000000000000

1 output(s) for total of 0.423283063492 xmr

stealth address amount amount idx tag
00: 4fadc53258ca00273466e021223efdc1518ffc6d17f61c385aa84bde452e8192 0.423283063492 90355 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": 48712, "vin": [ { "gen": { "height": 48702 } } ], "vout": [ { "amount": 423283063492, "target": { "key": "4fadc53258ca00273466e021223efdc1518ffc6d17f61c385aa84bde452e8192" } } ], "extra": [ 1, 251, 38, 158, 168, 122, 21, 45, 39, 27, 172, 64, 92, 34, 182, 180, 127, 118, 75, 67, 37, 186, 118, 8, 173, 127, 106, 252, 167, 189, 203, 99, 224, 2, 17, 0, 0, 0, 4, 34, 100, 175, 230, 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) | monero version: