← previous blocknext block →recent activity
Analyzing
Block #100,589,901
22 transactions · 21 stateful · 2026-08-30 22:32:53 UTC
Parallelism
68/100
Blocked
52%
Avg conflicts / tx
1.09
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,589,901 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w06w17w08w19w210w312w414w015w116w517w319w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x382434ca…96b5
0x34b655…2a6f
10 touches
10 conflicts
0xecd87a39…d9c5
0x34b655…2a6f
8 touches
6 conflicts
0x5b6af007…0f35
0x34b655…2a6f
8 touches
6 conflicts
0x8af736e2…714f
0x34b655…2a6f
8 touches
6 conflicts
0xbeb716e1…2f28
0x34b655…2a6f
8 touches
6 conflicts
0xccebf5c5…8758
0x34b655…2a6f
8 touches
6 conflicts
0xe99e18a9…058e
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
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 0x382434ca57…4d96b5
Audit this contract →
← previous block·next block →recent activity