Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a7f5ec92d5a7ca7fb3363f0bcf95bb9eba078ac64833ea40ff1d45bbab3b0da

Tx prefix hash: afbef27a4601075bc6c7599a6047ab95171faad910cd4786a66bb827bffd3753
Tx public key: df631c37ef0a418ef4e067374147dcad3a504af81b7438175238610dee96a03c
Timestamp: 1772384018 Timestamp [UTC]: 2026-03-01 16:53:38 Age [y:d:h:m:s]: 00:261:07:14:45
Block: 1488477 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192266 RingCT/type: yes/0
Extra: 01df631c37ef0a418ef4e067374147dcad3a504af81b7438175238610dee96a03c021100000005e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4a56011f4181d454dba45d5b27cc1a542f18bd3bdf1018c2f473779dd699e991 0.000600000000 1977955 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": 1488487, "vin": [ { "gen": { "height": 1488477 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a56011f4181d454dba45d5b27cc1a542f18bd3bdf1018c2f473779dd699e991" } } ], "extra": [ 1, 223, 99, 28, 55, 239, 10, 65, 142, 244, 224, 103, 55, 65, 71, 220, 173, 58, 80, 74, 248, 27, 116, 56, 23, 82, 56, 97, 13, 238, 150, 160, 60, 2, 17, 0, 0, 0, 5, 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: