Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6bbffb5030671e6adc804f102329e760f15a549e73b8ac0bf67c9f7bdcabeb7

Tx prefix hash: 57e2832767a442329fc81693d9061836c018abbafda70a58d90564572e0db0df
Tx public key: 81e6167bb13c103563cbb9fba03da86d57de649dd31e6c006d3bac1e15dea94f
Timestamp: 1574532334 Timestamp [UTC]: 2019-11-23 18:05:34 Age [y:d:h:m:s]: 06:364:10:52:09
Block: 15789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1667389 RingCT/type: yes/0
Extra: 0181e6167bb13c103563cbb9fba03da86d57de649dd31e6c006d3bac1e15dea94f02110000001a354bbe3b000000000000000000

1 output(s) for total of 0.544108326125 xmr

stealth address amount amount idx tag
00: d45db32e7351d86af5263fd6691f1e217eb6432932a6d01036a712f9b93506a9 0.544108326125 21456 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": 15799, "vin": [ { "gen": { "height": 15789 } } ], "vout": [ { "amount": 544108326125, "target": { "key": "d45db32e7351d86af5263fd6691f1e217eb6432932a6d01036a712f9b93506a9" } } ], "extra": [ 1, 129, 230, 22, 123, 177, 60, 16, 53, 99, 203, 185, 251, 160, 61, 168, 109, 87, 222, 100, 157, 211, 30, 108, 0, 109, 59, 172, 30, 21, 222, 169, 79, 2, 17, 0, 0, 0, 26, 53, 75, 190, 59, 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: