Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6fc698bb62abef7f3e5a7fa87a4eb49bb0b41ee3d4ab714a73058042050a7cf1

Tx prefix hash: 81aeb10b5450323141556397a5d742bdfc3d44459f6048b42a8758809f3435d5
Tx public key: dbfba85e66e8eef12f4a2955672fcdb04b30923704b0065f9c8beb670d7fa823
Timestamp: 1773175526 Timestamp [UTC]: 2026-03-10 20:45:26 Age [y:d:h:m:s]: 00:251:22:45:32
Block: 1495029 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185563 RingCT/type: yes/0
Extra: 01dbfba85e66e8eef12f4a2955672fcdb04b30923704b0065f9c8beb670d7fa823021100000006e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 20fd7a0e189bc0a0b9bff24871b97326631cd686db292a7547b69fe14f219834 0.000600000000 1984637 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": 1495039, "vin": [ { "gen": { "height": 1495029 } } ], "vout": [ { "amount": 600000000, "target": { "key": "20fd7a0e189bc0a0b9bff24871b97326631cd686db292a7547b69fe14f219834" } } ], "extra": [ 1, 219, 251, 168, 94, 102, 232, 238, 241, 47, 74, 41, 85, 103, 47, 205, 176, 75, 48, 146, 55, 4, 176, 6, 95, 156, 139, 235, 103, 13, 127, 168, 35, 2, 17, 0, 0, 0, 6, 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: