Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 948e960b02b4e56afcabf61f64424516e9141adf31f19736a9feb026c66d2a33

Tx prefix hash: 3be14617054d2b710ba23f7e23acd12e59f9f79c6168817ac9d34d3e1d5f3c4b
Tx public key: 0650c4eac9d1dc72a92e1d371b095f00c24ff5dd2560d97e5646e558281416e6
Timestamp: 1764511568 Timestamp [UTC]: 2025-11-30 14:06:08 Age [y:d:h:m:s]: 00:268:23:34:19
Block: 1423456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197990 RingCT/type: yes/0
Extra: 010650c4eac9d1dc72a92e1d371b095f00c24ff5dd2560d97e5646e558281416e6021100000001defb8f18000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d5af726f22f5c6ec4be7d70fa80dd8f04709cf514dcee8bef0a44029cb277967 0.000600000000 1912069 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": 1423466, "vin": [ { "gen": { "height": 1423456 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5af726f22f5c6ec4be7d70fa80dd8f04709cf514dcee8bef0a44029cb277967" } } ], "extra": [ 1, 6, 80, 196, 234, 201, 209, 220, 114, 169, 46, 29, 55, 27, 9, 95, 0, 194, 79, 245, 221, 37, 96, 217, 126, 86, 70, 229, 88, 40, 20, 22, 230, 2, 17, 0, 0, 0, 1, 222, 251, 143, 24, 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: