Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc8511e6ee7c54eb8705e786e272b75c5b0a2ccc8e4266019afff6004fe21796

Tx prefix hash: 767fbf861b2c70b38fa91b142ef964e1816c956692cd01c7a4768b731fbcf2b9
Tx public key: 7fb4ebe1f2653accf851be9f2bca958c4a9ad604183f8e41cf01498e7d6deb12
Timestamp: 1759433739 Timestamp [UTC]: 2025-10-02 19:35:39 Age [y:d:h:m:s]: 01:043:08:31:40
Block: 1381361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297269 RingCT/type: yes/0
Extra: 017fb4ebe1f2653accf851be9f2bca958c4a9ad604183f8e41cf01498e7d6deb12021100000004a5dccd79000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f120f469a6860f231ee580bd2831ff4a6a26d64b78d82e2df49eee9b4f02a529 0.000600000000 1869480 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": 1381371, "vin": [ { "gen": { "height": 1381361 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f120f469a6860f231ee580bd2831ff4a6a26d64b78d82e2df49eee9b4f02a529" } } ], "extra": [ 1, 127, 180, 235, 225, 242, 101, 58, 204, 248, 81, 190, 159, 43, 202, 149, 140, 74, 154, 214, 4, 24, 63, 142, 65, 207, 1, 73, 142, 125, 109, 235, 18, 2, 17, 0, 0, 0, 4, 165, 220, 205, 121, 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: