Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa07dcd8f53ba2e17f73bff32c84d89e660f2d0c1fc6a10e8672448eb4e4ca23

Tx prefix hash: 64800826b664053dd89c7575e047a8608d299795524271d09a13d42a3982e41d
Tx public key: 3767fcf4694eacb0072eeab45bd0df427480e1bbf6f1dba0aea10e5143f66e0d
Timestamp: 1783660091 Timestamp [UTC]: 2026-07-10 05:08:11 Age [y:d:h:m:s]: 00:135:07:42:12
Block: 1578861 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 104633 RingCT/type: yes/0
Extra: 013767fcf4694eacb0072eeab45bd0df427480e1bbf6f1dba0aea10e5143f66e0d020819aee52b9e52845a

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4c718f491f7fe03d8d67d8ea913c1e5141bc9f0e1ec51ae91b089e43e264dedf 0.000600000000 2068851 of 15 <1f>

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": 1578871, "vin": [ { "gen": { "height": 1578861 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "4c718f491f7fe03d8d67d8ea913c1e5141bc9f0e1ec51ae91b089e43e264dedf", "view_tag": "1f" } } } ], "extra": [ 1, 55, 103, 252, 244, 105, 78, 172, 176, 7, 46, 234, 180, 91, 208, 223, 66, 116, 128, 225, 187, 246, 241, 219, 160, 174, 161, 14, 81, 67, 246, 110, 13, 2, 8, 25, 174, 229, 43, 158, 82, 132, 90 ], "rct_signatures": { "type": 0 } }


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