← previous blocknext block →recent activity
Analyzing
Block #108,438,948
9 transactions · 8 stateful · 2026-09-27 10:15:57 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #108,438,948 · 9 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
4w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdbe7d14a…ecc3
0x34b655…2a6f
4 touches
1 conflict
0x908b3417…88d2
0x34b655…2a6f
4 touches
1 conflict
0xb58c5f09…1656
0x34b655…2a6f
4 touches
1 conflict
0xc99d7f64…a643
0x34b655…2a6f
4 touches
1 conflict
0xd453ac7e…7116
0x34b655…2a6f
4 touches
1 conflict
0x23769ebc…c8ed
0x34b655…2a6f
2 touches
0 conflicts
0x2c539d94…b63a
0x34b655…2a6f
2 touches
0 conflicts
0x31d88d27…7617
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 0xdbe7d14a4f…34ecc3
Audit this contract →
← previous block·next block →recent activity