← previous blocknext block →recent activity
Analyzing
Block #108,960,766
24 transactions · 20 stateful · 2026-09-29 06:07:05 UTC
Parallelism
75/100
Blocked
60%
Avg conflicts / tx
0.96
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,960,766 · 24 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
1w02w03w14w05w17w18w29w010w111w212w313w414w415w516w317w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd80cb602…d50a
0x34b655…2a6f
8 touches
6 conflicts
0x2b60abad…2240
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xa3ed5a09…c6d3
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x174f9ecc…6481
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x842db5f1…6d51
0x1b6862…e19c
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 0xd80cb6024c…7cd50a
Audit this contract →
← previous block·next block →recent activity