← previous blocknext block →recent activity
Analyzing
Block #105,542,271
21 transactions · 21 stateful · 2026-09-17 07:10:45 UTC
Parallelism
62/100
Blocked
52%
Avg conflicts / tx
1.81
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,542,271 · 21 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
1w02w13w04w15w08w09w111w212w314w115w416w417w518w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x86bd79a5…1f48
0x34b655…2a6f
14 touches
21 conflicts
0x53640669…9af1
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xb5f5f775…010b
0x34b655…2a6f
8 touches
6 conflicts
0xfd4e632c…e14c
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x9ff4ca89…6115
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