← previous blocknext block →recent activity
Analyzing
Block #108,503,856
16 transactions · 16 stateful · 2026-09-27 15:42:43 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #108,503,856 · 16 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
1w06w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf8b7e65f…2816
0x34b655…2a6f
4 touches
1 conflict
0x190b178a…c154
0x34b655…2a6f
4 touches
1 conflict
0x536dd201…42c2
0x34b655…2a6f
4 touches
1 conflict
0x908b3417…88d2
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd7c5101a…ecee
0x34b655…2a6f
4 touches
1 conflict
0x22badbc6…4c24
0x34b655…2a6f
2 touches
0 conflicts
0x3243e72f…1f6d
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 0xf8b7e65f29…052816
Audit this contract →
← previous block·next block →recent activity