Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 158f0646e641c962732810236d92ed1c0f8fd4d7203205bc554d3bbd5b85fe9b

Tx prefix hash: 2196a0a04d910150c7d95e2096c31e771667ec2ea2d0aa84ba650d4e193dd7dc
Tx public key: c59306c94b810f6cbc3715e595e330f221d12fb4f3b9aeb47c5588cc35b681aa
Timestamp: 1785094879 Timestamp [UTC]: 2026-07-26 19:41:19 Age [y:d:h:m:s]: 00:117:12:30:04
Block: 1593335 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 89937 RingCT/type: yes/0
Extra: 01c59306c94b810f6cbc3715e595e330f221d12fb4f3b9aeb47c5588cc35b681aa

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1ea9fb7e4ff5fd69c3b3d7b7593a42d002a6bb2f9b9f0407939456030e2c99a6 0.000600000000 2083353 of 15 <7e>

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": 1593345, "vin": [ { "gen": { "height": 1593335 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "1ea9fb7e4ff5fd69c3b3d7b7593a42d002a6bb2f9b9f0407939456030e2c99a6", "view_tag": "7e" } } } ], "extra": [ 1, 197, 147, 6, 201, 75, 129, 15, 108, 188, 55, 21, 229, 149, 227, 48, 242, 33, 209, 47, 180, 243, 185, 174, 180, 124, 85, 136, 204, 53, 182, 129, 170 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: