← previous blocknext block →recent activity
Analyzing
Block #108,495,606
25 transactions · 23 stateful · 2026-09-27 15:01:10 UTC
Parallelism
80/100
Blocked
43%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,495,606 · 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
3w04w15w26w310w011w112w013w014w115w116w217w318w224w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x125f12…a50b
10 touches
10 conflicts
0x8590b692…b267
0x34b655…2a6f
8 touches
6 conflicts
0xd9a9c481…8916
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xf06fce24…887d
0x34b655…2a6f
4 touches
1 conflict
0x5143e83a…af92
0x34b655…2a6f
4 touches
1 conflict
0x23769ebc…c8ed
0x34b655…2a6f
4 touches
1 conflict
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: 0x125f12a1…cda50b
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity