Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b5d3981792eaa726a4b41ce53d9d8bd2f6651d6753923a64dfa56dc44ef6d9c

Tx prefix hash: 3ee7075d84cdca11ed555e517860d9060f7fd9e3052863dab8a5a7bbe318874a
Tx public key: 2264790c05898c4eba6508e4bea0b3fc5263279d166079bce7401cd802d76dbc
Timestamp: 1711871933 Timestamp [UTC]: 2024-03-31 07:58:53 Age [y:d:h:m:s]: 02:045:23:13:00
Block: 990195 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 544748 RingCT/type: yes/0
Extra: 012264790c05898c4eba6508e4bea0b3fc5263279d166079bce7401cd802d76dbc02110000000752d47e94000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4cedd0defb2e2e722bfcd4548c392b4c0e79c71b22cc865bcbb81c7628d95f95 0.000600000000 1450517 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": 990205, "vin": [ { "gen": { "height": 990195 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4cedd0defb2e2e722bfcd4548c392b4c0e79c71b22cc865bcbb81c7628d95f95" } } ], "extra": [ 1, 34, 100, 121, 12, 5, 137, 140, 78, 186, 101, 8, 228, 190, 160, 179, 252, 82, 99, 39, 157, 22, 96, 121, 188, 231, 64, 28, 216, 2, 215, 109, 188, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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: