Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 998c1d557f0902b7a1539689a7ba20b8b0e08a2f21dbd192a61dfad0540cf24c

Tx prefix hash: d8a6e043476ed8f4f4bbea3989bc3be4ca89011c74c5b37f99db3717edd8b00d
Tx public key: 2f4934cf88b87d56f493a7afe5187dc874878f35ef197e4ae8face969aa3e6ac
Timestamp: 1744797065 Timestamp [UTC]: 2025-04-16 09:51:05 Age [y:d:h:m:s]: 01:033:03:25:53
Block: 1262629 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275651 RingCT/type: yes/0
Extra: 012f4934cf88b87d56f493a7afe5187dc874878f35ef197e4ae8face969aa3e6ac0211000000016c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9201793d0b4a6f5c66d703f2a316d722642ffe78212c3d3125d35111a430bcf5 0.000600000000 1749812 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": 1262639, "vin": [ { "gen": { "height": 1262629 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9201793d0b4a6f5c66d703f2a316d722642ffe78212c3d3125d35111a430bcf5" } } ], "extra": [ 1, 47, 73, 52, 207, 136, 184, 125, 86, 244, 147, 167, 175, 229, 24, 125, 200, 116, 135, 143, 53, 239, 25, 126, 74, 232, 250, 206, 150, 154, 163, 230, 172, 2, 17, 0, 0, 0, 1, 108, 152, 170, 61, 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: