← previous blocknext block →recent activity
Analyzing
Block #108,508,489
29 transactions · 26 stateful · 2026-09-27 16:06:02 UTC
Parallelism
86/100
Blocked
27%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,508,489 · 29 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w010w011w122w127w228w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5dc501b…831c
0x34b655…2a6f
8 touches
6 conflicts
0x7bd229ad…63b2
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x4aa8b305…4ace
0x860869…ff01
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x190b178a…c154
0x34b655…2a6f
4 touches
1 conflict
0x74e485b1…d380
0x34b655…2a6f
4 touches
1 conflict
0xeb91761f…427f
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
6 conflicts on slot 0xf5dc501bf7…74831c
Audit this contract →
← previous block·next block →recent activity