Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfb15cc95143abf1933681feb14db60a111d06040b0cffadfa8cfc2ec0d18683

Tx prefix hash: 96a9c95cf3e59be68f58ec1ac05f90473c2cde67dad2aaa8b99d706a1bd87bf0
Tx public key: 04be020b3ca062d059c434b39758504cdba5149e6915939ea43c1ecd71016a3e
Timestamp: 1770171711 Timestamp [UTC]: 2026-02-04 02:21:51 Age [y:d:h:m:s]: 00:286:21:47:05
Block: 1470203 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210540 RingCT/type: yes/0
Extra: 0104be020b3ca062d059c434b39758504cdba5149e6915939ea43c1ecd71016a3e021100000003e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4dba3f7b8be5adc5633efd3b51290c907a350b1e7ef871de2b803d6025c800f1 0.000600000000 1959471 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": 1470213, "vin": [ { "gen": { "height": 1470203 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4dba3f7b8be5adc5633efd3b51290c907a350b1e7ef871de2b803d6025c800f1" } } ], "extra": [ 1, 4, 190, 2, 11, 60, 160, 98, 208, 89, 196, 52, 179, 151, 88, 80, 76, 219, 165, 20, 158, 105, 21, 147, 158, 164, 60, 30, 205, 113, 1, 106, 62, 2, 17, 0, 0, 0, 3, 228, 245, 25, 63, 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: