← previous blocknext block →recent activity
Analyzing
Block #107,444,340
27 transactions · 22 stateful · 2026-09-23 22:48:01 UTC
Parallelism
81/100
Blocked
32%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,444,340 · 27 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w27w38w420w021w122w023w126w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a35acfb…d1b1
0x37db7f…ec7b
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x0311862a…7c5c
0x34b655…2a6f
4 touches
1 conflict
0xb127c451…050a
0x37db7f…ec7b
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0xe763a93c…e90b
0x34b655…2a6f
4 touches
1 conflict
0x051a10a8…7d4e
0x37db7f…ec7b
4 touches
1 conflict
0x56f91464…1e91
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
10 conflicts on slot 0x8a35acfbc1…6bd1b1
Audit this contract →
← previous block·next block →recent activity