Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2268507a5df020859d2d3813764491dcb911aa9c06c7f8e36d6ad5e9197b5db

Tx prefix hash: c8288b95a98c78ce8e42afd83c66b6cfc5a2cea7308c5621ce76898f3df32562
Tx public key: 87310945c1f6610666d8a3b5256df66156b523fd11487b3bba48554adeaaba50
Timestamp: 1719560621 Timestamp [UTC]: 2024-06-28 07:43:41 Age [y:d:h:m:s]: 01:324:04:26:37
Block: 1053913 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 482733 RingCT/type: yes/0
Extra: 0187310945c1f6610666d8a3b5256df66156b523fd11487b3bba48554adeaaba500211000000040011055b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f79e807a7070e2e1d2535eef6ac6ac9ee3bfe24e0ca58f5087fd33cd00029844 0.000600000000 1524266 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": 1053923, "vin": [ { "gen": { "height": 1053913 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f79e807a7070e2e1d2535eef6ac6ac9ee3bfe24e0ca58f5087fd33cd00029844" } } ], "extra": [ 1, 135, 49, 9, 69, 193, 246, 97, 6, 102, 216, 163, 181, 37, 109, 246, 97, 86, 181, 35, 253, 17, 72, 123, 59, 186, 72, 85, 74, 222, 170, 186, 80, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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: