Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd02ed77e2be37a880b0f1d6c54aff428f232e479e2cd52ea58a991971aab76f

Tx prefix hash: f64f3ceefb8e3bc77e3491db8a7ebd22568b1cb0bf238ee7104c37cee972f71c
Tx public key: c77104d5ab0d421256e5d15f6dd2e019dd5acad5db29b67c18de56be9594e012
Timestamp: 1774049124 Timestamp [UTC]: 2026-03-20 23:25:24 Age [y:d:h:m:s]: 00:239:14:21:59
Block: 1502232 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176709 RingCT/type: yes/0
Extra: 01c77104d5ab0d421256e5d15f6dd2e019dd5acad5db29b67c18de56be9594e012021100000002f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c7d867e531fb1574d1c4ae5835cbe726aaa92e5c579fe46ffcab7b0c55fd3ef7 0.000600000000 1991926 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": 1502242, "vin": [ { "gen": { "height": 1502232 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7d867e531fb1574d1c4ae5835cbe726aaa92e5c579fe46ffcab7b0c55fd3ef7" } } ], "extra": [ 1, 199, 113, 4, 213, 171, 13, 66, 18, 86, 229, 209, 95, 109, 210, 224, 25, 221, 90, 202, 213, 219, 41, 182, 124, 24, 222, 86, 190, 149, 148, 224, 18, 2, 17, 0, 0, 0, 2, 241, 136, 200, 168, 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: