← previous blocknext block →recent activity
Analyzing
Block #107,666,725
24 transactions · 21 stateful · 2026-09-24 17:28:36 UTC
Parallelism
75/100
Blocked
33%
Avg conflicts / tx
0.46
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,666,725 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w211w012w114w116w017w320w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ee42fad…93d9
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x122a4e67…118d
0x34b655…2a6f
4 touches
1 conflict
0x1393df1d…afbd
0x34b655…2a6f
4 touches
1 conflict
0x233517a5…45e5
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
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 0x5ee42fad2d…1e93d9
Audit this contract →
← previous block·next block →recent activity