Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b7ebd1dfc19b5c82610ade3814bb9ade70ab747bd68169ad3c406aba74c9f61

Tx prefix hash: c73b841997f2856097d1e24f17553c1f0493cd5c4c698ec1ae75c72c3853e226
Tx public key: f4da65eb1be80a09f43a8970b3036b210d7e42182a50366dbdfccdd192e5c8d3
Timestamp: 1742585530 Timestamp [UTC]: 2025-03-21 19:32:10 Age [y:d:h:m:s]: 01:243:06:00:13
Block: 1244319 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 437981 RingCT/type: yes/0
Extra: 01f4da65eb1be80a09f43a8970b3036b210d7e42182a50366dbdfccdd192e5c8d302110000000658cb2e2b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e235c9ce45a4e2663241489642e7d22ee84d96d87ec08bec5a5deb081290a6cb 0.000600000000 1731310 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": 1244329, "vin": [ { "gen": { "height": 1244319 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e235c9ce45a4e2663241489642e7d22ee84d96d87ec08bec5a5deb081290a6cb" } } ], "extra": [ 1, 244, 218, 101, 235, 27, 232, 10, 9, 244, 58, 137, 112, 179, 3, 107, 33, 13, 126, 66, 24, 42, 80, 54, 109, 189, 252, 205, 209, 146, 229, 200, 211, 2, 17, 0, 0, 0, 6, 88, 203, 46, 43, 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: