← previous blocknext block →recent activity
Analyzing
Block #108,619,104
32 transactions · 31 stateful · 2026-09-28 01:23:04 UTC
Parallelism
72/100
Blocked
48%
Avg conflicts / tx
1.09
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #108,619,104 · 32 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w06w07w19w110w213w214w315w416w518w120w621w722w123w226w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xa2c4d203…05b6
0x34b655…2a6f
8 touches
6 conflicts
0xffb026ea…d228
0x34b655…2a6f
6 touches
3 conflicts
0x45832512…41ee
0xd32edf…ff58
5 touches
3 conflicts
0xf35dca9e…bd8f
0x1b6862…e19c
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity