← previous blocknext block →recent activity
Analyzing
Block #108,439,216
13 transactions · 11 stateful · 2026-09-27 10:17:18 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #108,439,216 · 13 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc2fe6ed6…f8be
0x34b655…2a6f
4 touches
1 conflict
0x303bedc6…f887
0x34b655…2a6f
4 touches
1 conflict
0xea2a6eef…50b7
0x34b655…2a6f
4 touches
1 conflict
0x899b65d2…c8cd
0x34b655…2a6f
4 touches
1 conflict
0x9b419d78…018b
0x34b655…2a6f
4 touches
1 conflict
0x40d6d1e9…131e
0x34b655…2a6f
2 touches
0 conflicts
0x6d5d1fb5…86a7
0x34b655…2a6f
2 touches
0 conflicts
0xe226a0be…c046
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 0xc2fe6ed6dd…72f8be
Audit this contract →
← previous block·next block →recent activity