← previous blocknext block →recent activity
Analyzing
Block #108,344,137
26 transactions · 25 stateful · 2026-09-27 02:18:49 UTC
Parallelism
77/100
Blocked
24%
Avg conflicts / tx
0.46
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,344,137 · 26 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
1w07w111w212w313w222w024w425w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7bd229ad…63b2
0x34b655…2a6f
8 touches
6 conflicts
0xf5dc501b…831c
0x34b655…2a6f
8 touches
6 conflicts
0x22fc1fc2…e6ce
0x34b655…2a6f
6 touches
3 conflicts
0xb89574d6…1357
0x34b655…2a6f
6 touches
3 conflicts
0x48203298…65cb
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xaa61fe45…2c48
0x34b655…2a6f
4 touches
1 conflict
0xa05768d5…824e
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
6 conflicts on slot 0x7bd229ade5…6b63b2
Audit this contract →
← previous block·next block →recent activity