← previous blocknext block →recent activity
Analyzing
Block #108,482,638
20 transactions · 20 stateful · 2026-09-27 13:55:52 UTC
Parallelism
70/100
Blocked
35%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,482,638 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w08w19w010w111w212w313w416w518w019w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3d93ad2c…e747
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xba9f9225…2ead
0x34b655…2a6f
6 touches
3 conflicts
0x7bd229ad…63b2
0x34b655…2a6f
6 touches
3 conflicts
0x429c8b35…0f5c
0x34b655…2a6f
6 touches
3 conflicts
0xf5dc501b…831c
0x34b655…2a6f
6 touches
3 conflicts
0x699e0da0…32f7
0x34b655…2a6f
6 touches
3 conflicts
0xfdf9daab…bc92
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
10 conflicts on slot 0x3d93ad2c39…a6e747
Audit this contract →
← previous block·next block →recent activity