← previous blocknext block →recent activity
Analyzing
Block #108,641,323
33 transactions · 31 stateful · 2026-09-28 03:15:00 UTC
Parallelism
70/100
Blocked
65%
Avg conflicts / tx
1.88
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #108,641,323 · 33 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
1w02w13w24w35w07w419w520w623w727w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x33a238b9…0421
0xd32edf…ff58
9 touches
10 conflicts
0x68f7aaba…88df
0x34b655…2a6f
8 touches
6 conflicts
0xb81e6218…dd16
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xba9f9225…2ead
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
28 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity