Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c62d878e45d25f21d54e0d9e2158aa22a32784cca062c157bdeb2dae24f0fb0

Tx prefix hash: 9ec764ce25b385f2ba6f24d08ed6cba1fd3207a1a80f72116132340387b5f68f
Tx public key: 31128a7fa57c5682813c06386a6b4aa94db5090c4dc508c0064a2e19e1f83d57
Timestamp: 1579796450 Timestamp [UTC]: 2020-01-23 16:20:50 Age [y:d:h:m:s]: 06:113:11:07:56
Block: 51423 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1482656 RingCT/type: yes/0
Extra: 0131128a7fa57c5682813c06386a6b4aa94db5090c4dc508c0064a2e19e1f83d5702110000002e2264afe6000000000000000000

1 output(s) for total of 0.414586432173 xmr

stealth address amount amount idx tag
00: aa228f6b36522f999a754b359f85e5e1d3a4517e6a625c644d19611565141079 0.414586432173 95408 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": 51433, "vin": [ { "gen": { "height": 51423 } } ], "vout": [ { "amount": 414586432173, "target": { "key": "aa228f6b36522f999a754b359f85e5e1d3a4517e6a625c644d19611565141079" } } ], "extra": [ 1, 49, 18, 138, 127, 165, 124, 86, 130, 129, 60, 6, 56, 106, 107, 74, 169, 77, 181, 9, 12, 77, 197, 8, 192, 6, 74, 46, 25, 225, 248, 61, 87, 2, 17, 0, 0, 0, 46, 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: