← previous blocknext block →recent activity
Analyzing
Block #105,634,172
32 transactions · 27 stateful · 2026-09-17 14:53:22 UTC
Parallelism
72/100
Blocked
52%
Avg conflicts / tx
1.25
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #105,634,172 · 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
1w02w13w24w35w46w520w622w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x86bd79a5…1f48
0x34b655…2a6f
14 touches
21 conflicts
0x49890ced…6f23
0x34b655…2a6f
14 touches
21 conflicts
0xd99d25df…ecd8
0x34b655…2a6f
12 touches
15 conflicts
0xce44c489…c967
0x34b655…2a6f
12 touches
15 conflicts
0x88e92ec7…696d
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xe48402d6…728b
0x34b655…2a6f
6 touches
3 conflicts
0x748f197b…6d33
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
21 conflicts on slot 0x86bd79a5a6…961f48
Audit this contract →
← previous block·next block →recent activity