← previous blocknext block →recent activity
Analyzing
Block #107,817,262
26 transactions · 20 stateful · 2026-09-25 06:07:06 UTC
Parallelism
85/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,817,262 · 26 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w17w08w09w110w111w212w213w314w323w024w125w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa5811d93…8c73
0x34b655…2a6f
8 touches
6 conflicts
0xa75af083…801b
0x34b655…2a6f
8 touches
6 conflicts
0xbdd97c21…e3d0
0x34b655…2a6f
8 touches
6 conflicts
0x57db2399…c59e
0x34b655…2a6f
8 touches
6 conflicts
0x5e2ea201…12de
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x5cf4d55d…c588
0x34b655…2a6f
8 touches
6 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: Perpl
6 conflicts on slot 0xa5811d93b4…4d8c73
Audit this contract →
← previous block·next block →recent activity