← previous blocknext block →recent activity
Analyzing
Block #109,056,668
28 transactions · 23 stateful · 2026-09-29 14:11:43 UTC
Parallelism
86/100
Blocked
39%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #109,056,668 · 28 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
1w03w04w15w27w112w113w217w019w223w024w125w226w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x945d1dbe…e1d7
0xc8689a…ee79
6 touches
3 conflicts
0xa3f09358…6cde
0x34b655…2a6f
6 touches
3 conflicts
0xc4550172…3d03
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xdd9dc4b3…73b8
0x34b655…2a6f
6 touches
3 conflicts
0xfc8c9734…8019
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity