← previous blocknext block →recent activity
Analyzing
Block #107,440,596
10 transactions · 9 stateful · 2026-09-23 22:29:11 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #107,440,596 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x50e10826…843b
0x37db7f…ec7b
6 touches
3 conflicts
0x8a35acfb…d1b0
0x37db7f…ec7b
6 touches
3 conflicts
0x8a35acfb…d1b1
0x37db7f…ec7b
6 touches
3 conflicts
0xc009105d…96f7
0x37db7f…ec7b
6 touches
3 conflicts
0x8a35acfb…d1a6
0x37db7f…ec7b
4 touches
1 conflict
0x8a35acfb…d1a4
0x37db7f…ec7b
4 touches
1 conflict
0x56f91464…1e91
0x37db7f…ec7b
4 touches
1 conflict
0x640481cc…a2df
0x37db7f…ec7b
4 touches
1 conflict
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: 0x37db7fbf…3eec7b
3 conflicts on slot 0x50e1082618…a8843b
Audit this contract →
← previous block·next block →recent activity