Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24f8c038f6d2d82b870b40bd4064ddb0ad434c5c94b572200dcf0ffd7eef69d0

Tx prefix hash: d235525000daef46265d0f22e9c743cec0817d2a99b411286d545773bcac94df
Tx public key: 4cba5339199410f4a8356c1b61c02025971c781217065a0e1039183c900c832f
Timestamp: 1768201630 Timestamp [UTC]: 2026-01-12 07:07:10 Age [y:d:h:m:s]: 00:033:16:44:32
Block: 1454031 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 23930 RingCT/type: yes/0
Extra: 014cba5339199410f4a8356c1b61c02025971c781217065a0e1039183c900c832f021100000006215bbf89000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8ad796977ec22c3bd7a3a0b3b578494dd0d8cd2643b83612cb87cedb9f0b5161 0.000600000000 1943115 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": 1454041, "vin": [ { "gen": { "height": 1454031 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ad796977ec22c3bd7a3a0b3b578494dd0d8cd2643b83612cb87cedb9f0b5161" } } ], "extra": [ 1, 76, 186, 83, 57, 25, 148, 16, 244, 168, 53, 108, 27, 97, 192, 32, 37, 151, 28, 120, 18, 23, 6, 90, 14, 16, 57, 24, 60, 144, 12, 131, 47, 2, 17, 0, 0, 0, 6, 33, 91, 191, 137, 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) | dinastycoin version: tesla-369