Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df9c91575573943ed7ebd77ddd803e935cd91d8fe547445a9c165ee3ca0a1b41

Tx prefix hash: 84ccd609ea43078ac3f0b3b496898e716e30f07ee4a2863393c237c0b4f0de51
Tx public key: 4787cbb2e7a1bf694f6c4652114c7d826f23361b39a08f0d227d7435e358c044
Timestamp: 1582132000 Timestamp [UTC]: 2020-02-19 17:06:40 Age [y:d:h:m:s]: 06:278:01:11:07
Block: 68427 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1615067 RingCT/type: yes/0
Extra: 014787cbb2e7a1bf694f6c4652114c7d826f23361b39a08f0d227d7435e358c0440211000000027adf42d3000000000000000000

1 output(s) for total of 0.364144495626 xmr

stealth address amount amount idx tag
00: f7213eff25fd79db6ea03450dcbe0ec3f478832ac4b9c2f70d2e7fbe2bd41972 0.364144495626 126035 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": 68437, "vin": [ { "gen": { "height": 68427 } } ], "vout": [ { "amount": 364144495626, "target": { "key": "f7213eff25fd79db6ea03450dcbe0ec3f478832ac4b9c2f70d2e7fbe2bd41972" } } ], "extra": [ 1, 71, 135, 203, 178, 231, 161, 191, 105, 79, 108, 70, 82, 17, 76, 125, 130, 111, 35, 54, 27, 57, 160, 143, 13, 34, 125, 116, 53, 227, 88, 192, 68, 2, 17, 0, 0, 0, 2, 122, 223, 66, 211, 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: