← previous blocknext block →recent activity
Analyzing
Block #107,440,665
15 transactions · 15 stateful · 2026-09-23 22:29:32 UTC
Parallelism
80/100
Blocked
47%
Avg conflicts / tx
0.67
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #107,440,665 · 15 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
1w02w03w17w18w210w111w212w214w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xc657470d…37d2
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1b0
0x37db7f…ec7b
6 touches
3 conflicts
0x8a35acfb…d1b1
0x37db7f…ec7b
6 touches
3 conflicts
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x88cf2d31…3d64
0x34b655…2a6f
4 touches
1 conflict
0xa1c47168…d7ce
0x34b655…2a6f
4 touches
1 conflict
0xb6e66661…f5f5
0x34b655…2a6f
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: Perpl
3 conflicts on slot 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity