← previous blocknext block →recent activity
Analyzing
Block #108,840,111
20 transactions · 18 stateful · 2026-09-28 19:57:51 UTC
Parallelism
50/100
Blocked
56%
Avg conflicts / tx
1.9
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #108,840,111 · 20 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w09w111w112w213w314w415w516w617w718w819w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0xf5dc501b…831c
0x34b655…2a6f
10 touches
10 conflicts
0x7bd229ad…63b2
0x34b655…2a6f
10 touches
10 conflicts
0xd739490d…821e
0x34b655…2a6f
8 touches
9 conflicts
0xa96f93f2…11f6
0x34b655…2a6f
8 touches
6 conflicts
0xa69bb4e1…f2bb
0x34b655…2a6f
8 touches
6 conflicts
0xb723f58a…3914
0x34b655…2a6f
5 touches
3 conflicts
0xb8337efb…68ca
0x34b655…2a6f
5 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
36 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity