← previous blocknext block →recent activity
Analyzing
Block #108,619,097
28 transactions · 22 stateful · 2026-09-28 01:23:02 UTC
Parallelism
64/100
Blocked
50%
Avg conflicts / tx
0.86
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #108,619,097 · 28 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w06w09w110w211w312w418w520w621w022w123w125w726w827w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x724ba0cf…01c7
0x34b655…2a6f
10 touches
10 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x280aaa58…1c52
0x34b655…2a6f
8 touches
6 conflicts
0x309f47c0…e1cf
0x34b655…2a6f
8 touches
6 conflicts
0x3b65c5ca…9f83
0x34b655…2a6f
8 touches
6 conflicts
0x3d354577…342d
0x34b655…2a6f
8 touches
6 conflicts
0x434ddf72…de6a
0x34b655…2a6f
8 touches
6 conflicts
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
10 conflicts on slot 0x724ba0cf22…b301c7
Audit this contract →
← previous block·next block →recent activity