← previous blocknext block →recent activity
Analyzing
Block #107,823,238
17 transactions · 17 stateful · 2026-09-25 06:37:11 UTC
Parallelism
53/100
Blocked
41%
Avg conflicts / tx
1.06
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #107,823,238 · 17 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w49w510w611w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xd1fc7ab7…c52b
0x34b655…2a6f
8 touches
6 conflicts
0xdcd07321…1c31
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x90a021f0…f922
0x34b655…2a6f
6 touches
3 conflicts
0xba9f9225…2ead
0x34b655…2a6f
6 touches
3 conflicts
0x41eb76a7…6483
0x34b655…2a6f
4 touches
1 conflict
0x422cccbc…9b18
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
6 conflicts on slot 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity