Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c205a41d394fd91c90348ad2b1d723cf0265fbd69dba7a9a60dc63affe87fa85

Tx prefix hash: 677214c3ac38803ee7aba37e6b456bdb867973ee8cadf4e4f2b74e80589dc229
Tx public key: bd85f9d61a48f0882a8bcc27b8aee4b50a411546a3570887d222252cbb32715a
Timestamp: 1773752046 Timestamp [UTC]: 2026-03-17 12:54:06 Age [y:d:h:m:s]: 00:242:00:36:11
Block: 1499788 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178382 RingCT/type: yes/0
Extra: 01bd85f9d61a48f0882a8bcc27b8aee4b50a411546a3570887d222252cbb32715a021100000001e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 81d67ee02bc5efefbeefa4d5416f623a655238751b9dd8abe0a50c6812055a29 0.000600000000 1989452 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": 1499798, "vin": [ { "gen": { "height": 1499788 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81d67ee02bc5efefbeefa4d5416f623a655238751b9dd8abe0a50c6812055a29" } } ], "extra": [ 1, 189, 133, 249, 214, 26, 72, 240, 136, 42, 139, 204, 39, 184, 174, 228, 181, 10, 65, 21, 70, 163, 87, 8, 135, 210, 34, 37, 44, 187, 50, 113, 90, 2, 17, 0, 0, 0, 1, 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: