← previous blocknext block →recent activity
Analyzing
Block #108,576,230
21 transactions · 20 stateful · 2026-09-27 21:47:13 UTC
Parallelism
62/100
Blocked
35%
Avg conflicts / tx
1.14
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #108,576,230 · 21 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
2w03w14w25w317w418w519w620w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5dc501b…831c
0x34b655…2a6f
14 touches
21 conflicts
0x7bd229ad…63b2
0x34b655…2a6f
14 touches
21 conflicts
0xa69bb4e1…f2bb
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x6a907841…d565
0x34b655…2a6f
5 touches
3 conflicts
0xd739490d…821e
0x34b655…2a6f
5 touches
3 conflicts
0x89c20ff4…36a4
0x34b655…2a6f
4 touches
1 conflict
0xb3a29ff5…9174
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
21 conflicts on slot 0xf5dc501bf7…74831c
Audit this contract →
← previous block·next block →recent activity