← previous blocknext block →recent activity
Analyzing
Block #108,275,670
23 transactions · 20 stateful · 2026-09-26 20:34:16 UTC
Parallelism
87/100
Blocked
40%
Avg conflicts / tx
0.48
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,275,670 · 23 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w111w012w115w016w117w220w221w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xf5dc501b…831c
0x34b655…2a6f
6 touches
3 conflicts
0x7bd229ad…63b2
0x34b655…2a6f
6 touches
3 conflicts
0x37f98106…f8ae
0x065c9d…c394
5 touches
3 conflicts
0x00000000…0000
0x33a247…6221
4 touches
1 conflict
0x015e9cc2…69d0
0x33a247…6221
4 touches
1 conflict
0x599944b2…d19f
0x33a247…6221
4 touches
1 conflict
0xe0826906…21db
0x33a247…6221
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity