Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe8ff1f5fc621140f590cf0ea1ac95e3452fc3bd7a8e739cfe755374c304c2fc

Tx prefix hash: 9556d24602ad650460fa29568d30209633ffe76f0f466b5600f2d9fed56ea2d8
Tx public key: 9d7cba53cce175682b76dc8d2b8908e890f7cbe918f14fa05ef89dba3e0121d4
Timestamp: 1760285570 Timestamp [UTC]: 2025-10-12 16:12:50 Age [y:d:h:m:s]: 01:036:22:17:58
Block: 1388426 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292763 RingCT/type: yes/0
Extra: 019d7cba53cce175682b76dc8d2b8908e890f7cbe918f14fa05ef89dba3e0121d4021100000001d8e7d241000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fc338f0e3997461740ad7e29eb1b187693eb4f03410fc9dde9d42b9d84b5e2a9 0.000600000000 1876635 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": 1388436, "vin": [ { "gen": { "height": 1388426 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc338f0e3997461740ad7e29eb1b187693eb4f03410fc9dde9d42b9d84b5e2a9" } } ], "extra": [ 1, 157, 124, 186, 83, 204, 225, 117, 104, 43, 118, 220, 141, 43, 137, 8, 232, 144, 247, 203, 233, 24, 241, 79, 160, 94, 248, 157, 186, 62, 1, 33, 212, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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: