Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8eddd04c8d424e43bd08af3ee7ad5c7f7babfeb54d59674f69559dbf63cbc918

Tx prefix hash: c9f8f59d1f3c33553ecee35b8b6a4361496c3c830d694edbf46179f530937c74
Tx public key: bece6d2517ec79c980de69bd62b544c23cc79d5da4e31d4a9405b14304442dd9
Timestamp: 1773241984 Timestamp [UTC]: 2026-03-11 15:13:04 Age [y:d:h:m:s]: 00:253:02:55:56
Block: 1495577 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186484 RingCT/type: yes/0
Extra: 01bece6d2517ec79c980de69bd62b544c23cc79d5da4e31d4a9405b14304442dd9021100000002e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bfda29aba4f307ad266f5d42f6c53fae8d0498d1c9cd5b364365d542386147f2 0.000600000000 1985189 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": 1495587, "vin": [ { "gen": { "height": 1495577 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bfda29aba4f307ad266f5d42f6c53fae8d0498d1c9cd5b364365d542386147f2" } } ], "extra": [ 1, 190, 206, 109, 37, 23, 236, 121, 201, 128, 222, 105, 189, 98, 181, 68, 194, 60, 199, 157, 93, 164, 227, 29, 74, 148, 5, 177, 67, 4, 68, 45, 217, 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: