← previous blocknext block →recent activity
Analyzing
Block #109,237,602
11 transactions · 11 stateful · 2026-09-30 05:23:17 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #109,237,602 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w18w09w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x2ddc3e4c…bd7c
0x34b655…2a6f
2 touches
0 conflicts
0x2f8a747a…be23
0x34b655…2a6f
2 touches
0 conflicts
0x3d970fa3…3bc7
0x34b655…2a6f
2 touches
0 conflicts
0x560b6fd9…a104
0x34b655…2a6f
2 touches
0 conflicts
0x58940b94…acb3
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity