Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 049192d8e969b31d2f60107a376e98b610df070dc9342e52d57794f86c2c1776

Tx prefix hash: a59a63330879c05f697706f604774779aa430622439844774f9262176908d7e1
Tx public key: 54f3420a31f18b1228b5f340548e81c1e640f40a2481c884d7501f91f164d9b1
Timestamp: 1745598290 Timestamp [UTC]: 2025-04-25 16:24:50 Age [y:d:h:m:s]: 01:019:13:09:52
Block: 1269267 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 264881 RingCT/type: yes/0
Extra: 0154f3420a31f18b1228b5f340548e81c1e640f40a2481c884d7501f91f164d9b10211000000016c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3771b83346fc600f70312e8c9d03c84d40dad4e70d2dbc1f581cb890b2bf159a 0.000600000000 1756502 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": 1269277, "vin": [ { "gen": { "height": 1269267 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3771b83346fc600f70312e8c9d03c84d40dad4e70d2dbc1f581cb890b2bf159a" } } ], "extra": [ 1, 84, 243, 66, 10, 49, 241, 139, 18, 40, 181, 243, 64, 84, 142, 129, 193, 230, 64, 244, 10, 36, 129, 200, 132, 215, 80, 31, 145, 241, 100, 217, 177, 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: