← previous blocknext block →recent activity
Analyzing
Block #108,509,937
12 transactions · 11 stateful · 2026-09-27 16:13:20 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #108,509,937 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5dc501b…831c
0x34b655…2a6f
4 touches
1 conflict
0x7bd229ad…63b2
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0215d8e5…68d5
0x34b655…2a6f
2 touches
0 conflicts
0x13366c0b…fc6a
0x34b655…2a6f
2 touches
0 conflicts
0x1ad75f5e…b869
0x34b655…2a6f
2 touches
0 conflicts
0x1c732a14…3a4e
0x34b655…2a6f
2 touches
0 conflicts
0x2f8aa350…ed4a
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
1 conflict on slot 0xf5dc501bf7…74831c
Audit this contract →
← previous block·next block →recent activity