← previous blocknext block →recent activity
Analyzing
Block #108,278,699
25 transactions · 22 stateful · 2026-09-26 20:49:31 UTC
Parallelism
68/100
Blocked
41%
Avg conflicts / tx
0.84
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #108,278,699 · 25 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
1w02w04w16w213w317w418w419w520w621w722w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xedc39209…aff6
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x5969523e…5191
0x34b655…2a6f
6 touches
3 conflicts
0x945d1dbe…e1d7
0xc8689a…ee79
6 touches
3 conflicts
0x55cde02d…89cb
0x34b655…2a6f
6 touches
3 conflicts
0xe226a0be…c046
0x34b655…2a6f
6 touches
3 conflicts
0xf0f268e4…bbc1
0x34b655…2a6f
6 touches
3 conflicts
0x238d0a65…428b
0x37db7f…ec7b
6 touches
3 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 0xedc3920934…94aff6
Audit this contract →
← previous block·next block →recent activity