← previous blocknext block →recent activity
Analyzing
Block #105,881,553
20 transactions · 20 stateful · 2026-09-18 11:39:52 UTC
Parallelism
75/100
Blocked
35%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,881,553 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w06w17w28w316w018w119w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x97e4c862…4419
0x34b655…2a6f
10 touches
10 conflicts
0x18616ad3…7bf5
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x206f4379…e08a
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc389d1ff…6a00
0x34b655…2a6f
6 touches
3 conflicts
0xed863ec8…90d6
0x1b6862…e19c
4 touches
1 conflict
0x0f65f95e…37fc
0x34b655…2a6f
4 touches
1 conflict
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 0x97e4c86258…af4419
Audit this contract →
← previous block·next block →recent activity