Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b9d956d2bc33c43317230dc1cb4ff16342571860897ff671b1bf44f1aeb9591

Tx prefix hash: 56ad6451d7380961a561293b83c118ea42a0786ebf9332be3d882839a54402cc
Tx public key: 8ca07978d7b8d00084ec755f8d46531581f010391ae6e5188dbe452bbaba486f
Timestamp: 1739229085 Timestamp [UTC]: 2025-02-10 23:11:25 Age [y:d:h:m:s]: 01:095:09:11:39
Block: 1216539 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319194 RingCT/type: yes/0
Extra: 018ca07978d7b8d00084ec755f8d46531581f010391ae6e5188dbe452bbaba486f02110000000f1f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 06b34c1fbd50f4bcbb90e6daf7e77373823ae2e53f3b4ef7d1bfe93586d5ae6b 0.000600000000 1703346 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": 1216549, "vin": [ { "gen": { "height": 1216539 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06b34c1fbd50f4bcbb90e6daf7e77373823ae2e53f3b4ef7d1bfe93586d5ae6b" } } ], "extra": [ 1, 140, 160, 121, 120, 215, 184, 208, 0, 132, 236, 117, 95, 141, 70, 83, 21, 129, 240, 16, 57, 26, 230, 229, 24, 141, 190, 69, 43, 186, 186, 72, 111, 2, 17, 0, 0, 0, 15, 31, 10, 83, 235, 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: