Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f3ba6be2a4d96cedca3acaa996970c3acd22007df6bbaf3ab70e478be264751

Tx prefix hash: 767f5c1eef04059fcef860797aa9d1d7c6cfcaf549f25e100713094f19f0e975
Tx public key: 4cc608da3611b28af38139190fa968ad9ade78d7fda36b5a6a988f541f7b0096
Timestamp: 1771668107 Timestamp [UTC]: 2026-02-21 10:01:47 Age [y:d:h:m:s]: 00:266:12:58:07
Block: 1482560 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195904 RingCT/type: yes/0
Extra: 014cc608da3611b28af38139190fa968ad9ade78d7fda36b5a6a988f541f7b0096021100000002e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e7bbd2e5918a60d0e76ee6adc21e8d3419097543b8040303ce5a56d5fe124017 0.000600000000 1971954 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": 1482570, "vin": [ { "gen": { "height": 1482560 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7bbd2e5918a60d0e76ee6adc21e8d3419097543b8040303ce5a56d5fe124017" } } ], "extra": [ 1, 76, 198, 8, 218, 54, 17, 178, 138, 243, 129, 57, 25, 15, 169, 104, 173, 154, 222, 120, 215, 253, 163, 107, 90, 106, 152, 143, 84, 31, 123, 0, 150, 2, 17, 0, 0, 0, 2, 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: