← previous blocknext block →recent activity
Analyzing
Block #105,931,181
18 transactions · 16 stateful · 2026-09-18 15:50:32 UTC
Parallelism
61/100
Blocked
56%
Avg conflicts / tx
1.33
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,931,181 · 18 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
1w02w13w14w27w28w310w411w512w616w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x310e4f33…f88a
0x34b655…2a6f
10 touches
10 conflicts
0xe796f8b7…ad55
0x34b655…2a6f
10 touches
10 conflicts
0xd79c9727…1233
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x08d2e11a…9c15
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x30ae635d…5e67
0x34b655…2a6f
6 touches
3 conflicts
0xa35509fa…5cb3
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 0x310e4f33e6…c5f88a
Audit this contract →
← previous block·next block →recent activity