← previous blocknext block →recent activity
Analyzing
Block #107,813,161
24 transactions · 18 stateful · 2026-09-25 05:46:28 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
0.75
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #107,813,161 · 24 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
4w06w110w011w112w213w314w415w516w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0xa23b9051…392f
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x2d3b7177…566a
0x34b655…2a6f
4 touches
1 conflict
0x46f2ebac…94e6
0x34b655…2a6f
4 touches
1 conflict
0x5fb32549…8586
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