Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 15ef6bbeb690ca12c3f2b0cf71ac8871ad98ddecaa2e01b975dd6d4b5ac4a5f9

Tx prefix hash: 649b3865ff87b1da51b22b51d8db027421c2bd85d0626f2035915a903e78d93f
Tx public key: a93e539f817ab54f171d505e292361a4a3a7b497c9dde6884c7de8fb1bbcf88f
Timestamp: 1772104181 Timestamp [UTC]: 2026-02-26 11:09:41 Age [y:d:h:m:s]: 00:264:08:38:30
Block: 1486150 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194448 RingCT/type: yes/0
Extra: 01a93e539f817ab54f171d505e292361a4a3a7b497c9dde6884c7de8fb1bbcf88f021100000004e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f42f8d0ffe30756910ea72622cbdb41c1ffff5f3a7e5c92a818b98ad34b1c227 0.000600000000 1975594 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": 1486160, "vin": [ { "gen": { "height": 1486150 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f42f8d0ffe30756910ea72622cbdb41c1ffff5f3a7e5c92a818b98ad34b1c227" } } ], "extra": [ 1, 169, 62, 83, 159, 129, 122, 181, 79, 23, 29, 80, 94, 41, 35, 97, 164, 163, 167, 180, 151, 201, 221, 230, 136, 76, 125, 232, 251, 27, 188, 248, 143, 2, 17, 0, 0, 0, 4, 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: