← previous blocknext block →recent activity

Analyzing

Block #75,216,193

11 transactions · 9 stateful · 2026-05-17 16:11:28 UTC

Parallelism

82/100

Blocked

22%

Avg conflicts / tx

0.18

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,216,193  ·  11 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x765c236f…ff45

0x2a68ba…90c5

4 touches
1 conflict

0xba38536d…2b7d

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x84ca05b9…d0fc

0x065c9d…c394

3 touches
1 conflict

0x5a55e68c…47ad

0x065c9d…c394

2 touches
0 conflicts

0xe982e141…cfb4

0x065c9d…c394

2 touches
0 conflicts

0xf0b7c810…1727

0x065c9d…c394

2 touches
0 conflicts

0xf0c57153…9c09

0x065c9d…c394

2 touches
0 conflicts

What's blocking what?

Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.

The bottleneck

Throughput-killer: 0x2a68ba18…8e90c5

1 conflict on slot 0x765c236f2d…b5ff45

← previous block·next block →recent activity