Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d77a491319ed48b18b8565299316ac02280d7aecc00ce4fd92285cdcb44df64

Tx prefix hash: f50b1c315d98bd6cfc1adca8829b795db9bfb857a2ef66e672b247e5f9bc27cb
Tx public key: fd205fab9d10e7cf80340ee90abc961b82a53ab23ee52bd4c42a8bf5e4e82088
Timestamp: 1771972255 Timestamp [UTC]: 2026-02-24 22:30:55 Age [y:d:h:m:s]: 00:268:21:53:44
Block: 1485084 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197835 RingCT/type: yes/0
Extra: 01fd205fab9d10e7cf80340ee90abc961b82a53ab23ee52bd4c42a8bf5e4e82088021100000001e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 55a92f66cf15ed72112bafeef4d44c376f0340f2159c7b48d1d10e172714c290 0.000600000000 1974516 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": 1485094, "vin": [ { "gen": { "height": 1485084 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55a92f66cf15ed72112bafeef4d44c376f0340f2159c7b48d1d10e172714c290" } } ], "extra": [ 1, 253, 32, 95, 171, 157, 16, 231, 207, 128, 52, 14, 233, 10, 188, 150, 27, 130, 165, 58, 178, 62, 229, 43, 212, 196, 42, 139, 245, 228, 232, 32, 136, 2, 17, 0, 0, 0, 1, 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: