Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a202f4f019072afba3275ecaf4c6bea0cbd1e5d08563bcce4cacbd1d60f712e

Tx prefix hash: 1949ba46db18e17b0735ebf9b6613b5d4c6db53f630d976fc016254bfc486f0f
Tx public key: 193399408415fa9aaad00ab49c0fedd8e34b63164ad85370d20b85a9498a3d7f
Timestamp: 1772210444 Timestamp [UTC]: 2026-02-27 16:40:44 Age [y:d:h:m:s]: 00:266:13:34:04
Block: 1487043 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196174 RingCT/type: yes/0
Extra: 01193399408415fa9aaad00ab49c0fedd8e34b63164ad85370d20b85a9498a3d7f021100000002e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1db7626f09f31920a67a6e4be252877fb2779883e1c9b57b41eeafcef473f985 0.000600000000 1976505 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": 1487053, "vin": [ { "gen": { "height": 1487043 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1db7626f09f31920a67a6e4be252877fb2779883e1c9b57b41eeafcef473f985" } } ], "extra": [ 1, 25, 51, 153, 64, 132, 21, 250, 154, 170, 208, 10, 180, 156, 15, 237, 216, 227, 75, 99, 22, 74, 216, 83, 112, 210, 11, 133, 169, 73, 138, 61, 127, 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: