Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 019bf8cdd6bd3ec9796ef027e5965cf1307648db7403d1f05c4a58a72e02482e

Tx prefix hash: 8cafb66c38e33116eac44fe1d80500080ef5c6981d1e46231365a66b8ab227b9
Tx public key: 859a9bfb8737bd0b5e519c9682e88017fa1e28d77f02c0d2aea4877e23263212
Timestamp: 1577518363 Timestamp [UTC]: 2019-12-28 07:32:43 Age [y:d:h:m:s]: 06:330:15:09:34
Block: 33257 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1650237 RingCT/type: yes/0
Extra: 01859a9bfb8737bd0b5e519c9682e88017fa1e28d77f02c0d2aea4877e232632120211000000054ac5aa02000000000000000000

1 output(s) for total of 0.476227111738 xmr

stealth address amount amount idx tag
00: fb78100b569ac943650a788da09a8fcdbd1020bd33b82414a38d6fad00a60d46 0.476227111738 55644 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": 33267, "vin": [ { "gen": { "height": 33257 } } ], "vout": [ { "amount": 476227111738, "target": { "key": "fb78100b569ac943650a788da09a8fcdbd1020bd33b82414a38d6fad00a60d46" } } ], "extra": [ 1, 133, 154, 155, 251, 135, 55, 189, 11, 94, 81, 156, 150, 130, 232, 128, 23, 250, 30, 40, 215, 127, 2, 192, 210, 174, 164, 135, 126, 35, 38, 50, 18, 2, 17, 0, 0, 0, 5, 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) | monero version: