← previous blocknext block →recent activity
Analyzing
Block #108,619,156
29 transactions · 26 stateful · 2026-09-28 01:23:20 UTC
Parallelism
72/100
Blocked
38%
Avg conflicts / tx
0.97
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #108,619,156 · 29 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w010w114w115w216w317w420w421w522w623w728w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe894d22d…500f
0x34b655…2a6f
10 touches
10 conflicts
0xf16147e8…2ec1
0xd32edf…ff58
9 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x66fc0764…05fd
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x70986451…c6bd
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xcc844ab5…4c6d
0x34b655…2a6f
6 touches
3 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 0xe894d22dcc…10500f
Audit this contract →
← previous block·next block →recent activity