← previous blocknext block →recent activity
Analyzing
Block #108,960,254
20 transactions · 18 stateful · 2026-09-29 06:04:26 UTC
Parallelism
70/100
Blocked
39%
Avg conflicts / tx
0.6
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,960,254 · 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
2w03w15w06w19w010w111w212w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3ad68b1c…f401
0x34b655…2a6f
6 touches
3 conflicts
0x9375a764…dca1
0x34b655…2a6f
6 touches
3 conflicts
0x31d88d27…7617
0x34b655…2a6f
6 touches
3 conflicts
0xafb7138a…23ce
0x34b655…2a6f
6 touches
3 conflicts
0xbefdde57…cd0e
0x34b655…2a6f
6 touches
3 conflicts
0xc4c059d8…185d
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
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
3 conflicts on slot 0x3ad68b1cf7…1bf401
Audit this contract →
← previous block·next block →recent activity