← previous blocknext block →recent activity
Analyzing
Block #108,564,548
24 transactions · 22 stateful · 2026-09-27 20:48:25 UTC
Parallelism
67/100
Blocked
41%
Avg conflicts / tx
1.29
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #108,564,548 · 24 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
1w02w13w04w05w113w214w315w417w518w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3631c8f9…0787
0x34b655…2a6f
14 touches
21 conflicts
0xf6deafb5…5c25
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x2029b74e…c206
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x7462b8f2…6312
0x34b655…2a6f
8 touches
6 conflicts
0x7497cad2…f3f3
0x34b655…2a6f
8 touches
6 conflicts
0x6f79b6c9…b589
0x34b655…2a6f
6 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
21 conflicts on slot 0x3631c8f978…980787
Audit this contract →
← previous block·next block →recent activity