← previous blocknext block →recent activity
Analyzing
Block #108,279,091
25 transactions · 24 stateful · 2026-09-26 20:51:29 UTC
Parallelism
76/100
Blocked
33%
Avg conflicts / tx
0.44
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,279,091 · 25 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
1w05w06w17w212w016w117w120w021w122w323w424w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x3a663e9a…a9c5
0x508254…98bd
4 touches
1 conflict
0xa770eaaf…d6f0
0x508254…98bd
4 touches
1 conflict
0xe1c4d8e8…ffa8
0x508254…98bd
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x045532dd…4b7d
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity