Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8190fece32b443807e0f76e1dd89556d2eebe6e9c81868685a134cd244d43295

Tx prefix hash: 2b6da9d413c1f4872176c5df42a70637efa70eb5e2622014a861b5b9d9347e14
Tx public key: c911a4cc20d1caf5f1ab2b90f8a1c88de8fb7673e81de5e87b2416e8452d9c43
Timestamp: 1781294105 Timestamp [UTC]: 2026-06-12 19:55:05 Age [y:d:h:m:s]: 00:161:04:39:04
Block: 1557753 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 125291 RingCT/type: yes/0
Extra: 01c911a4cc20d1caf5f1ab2b90f8a1c88de8fb7673e81de5e87b2416e8452d9c43

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d6bf251571025636f15b1b4591a4ea8b3a4d32836ee41cbe087358363cb7f1c4 0.000600000000 2047731 of 15 <b7>

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": 1557763, "vin": [ { "gen": { "height": 1557753 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "d6bf251571025636f15b1b4591a4ea8b3a4d32836ee41cbe087358363cb7f1c4", "view_tag": "b7" } } } ], "extra": [ 1, 201, 17, 164, 204, 32, 209, 202, 245, 241, 171, 43, 144, 248, 161, 200, 141, 232, 251, 118, 115, 232, 29, 229, 232, 123, 36, 22, 232, 69, 45, 156, 67 ], "rct_signatures": { "type": 0 } }


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