Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ada4bdc8b421c6ef48cd34f292af9bf885c8051091159dbdbde2fb0944f1272

Tx prefix hash: 900ad50d16f58f649457f751dce83f3e4e90e63bbf8ae60761fd3d7aa020bd93
Tx public key: c194f438da2392042a22d06fd37eecebbf262f5ca20ed70ac4b9fe12a22f38c6
Timestamp: 1787183615 Timestamp [UTC]: 2026-08-19 23:53:35 Age [y:d:h:m:s]: 00:090:03:07:22
Block: 1617113 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 63717 RingCT/type: yes/0
Extra: 01c194f438da2392042a22d06fd37eecebbf262f5ca20ed70ac4b9fe12a22f38c60208be38392565e94e42

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4062bce0bcc54c11f1d8db8beb6ff27c6535cebba23c60c371ad8026287f0624 0.000600000000 2107133 of 15 <67>

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": 1617123, "vin": [ { "gen": { "height": 1617113 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "4062bce0bcc54c11f1d8db8beb6ff27c6535cebba23c60c371ad8026287f0624", "view_tag": "67" } } } ], "extra": [ 1, 193, 148, 244, 56, 218, 35, 146, 4, 42, 34, 208, 111, 211, 126, 236, 235, 191, 38, 47, 92, 162, 14, 215, 10, 196, 185, 254, 18, 162, 47, 56, 198, 2, 8, 190, 56, 57, 37, 101, 233, 78, 66 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: