← previous blocknext block →recent activity
Analyzing
Block #108,646,493
25 transactions · 23 stateful · 2026-09-28 03:41:02 UTC
Parallelism
80/100
Blocked
39%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,646,493 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w06w07w19w010w112w014w115w216w317w419w122w023w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7bd229ad…63b2
0x34b655…2a6f
10 touches
10 conflicts
0xf5dc501b…831c
0x34b655…2a6f
10 touches
10 conflicts
0x3a663e9a…a9c7
0x508254…98bd
6 touches
3 conflicts
0x3a663e9a…a9cb
0x508254…98bd
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x564d349e…744e
0x34b655…2a6f
4 touches
1 conflict
0x6ca15e14…7be8
0x34b655…2a6f
4 touches
1 conflict
0x7eba5e98…49f7
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
10 conflicts on slot 0x7bd229ade5…6b63b2
Audit this contract →
← previous block·next block →recent activity