Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0018d13aa6a219d4f8757fc21cc577c310d4016784dba1ae2cb9a6776c7b72b0

Tx prefix hash: 52853f7b991657db5b2bda4fa09030043a4938f5cb418e98e65312366ef777a7
Tx public key: 6ce95afad3b4b5d11d6cf752e2da0f371f22d54b48c83178a3731b2291b910d4
Timestamp: 1709779402 Timestamp [UTC]: 2024-03-07 02:43:22 Age [y:d:h:m:s]: 02:136:01:34:33
Block: 972830 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 610284 RingCT/type: yes/0
Extra: 016ce95afad3b4b5d11d6cf752e2da0f371f22d54b48c83178a3731b2291b910d402110000000659dad3f5000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 855ffb0c8900ed483a32e0109b04481dfdfe8423b2b14bb28fd2efeaeafce930 0.000600000000 1432749 of 15 -

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": 972840, "vin": [ { "gen": { "height": 972830 } } ], "vout": [ { "amount": 600000000, "target": { "key": "855ffb0c8900ed483a32e0109b04481dfdfe8423b2b14bb28fd2efeaeafce930" } } ], "extra": [ 1, 108, 233, 90, 250, 211, 180, 181, 209, 29, 108, 247, 82, 226, 218, 15, 55, 31, 34, 213, 75, 72, 200, 49, 120, 163, 115, 27, 34, 145, 185, 16, 212, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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: