← previous blocknext block →recent activity
Analyzing
Block #105,841,955
14 transactions · 14 stateful · 2026-09-18 08:20:27 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,841,955 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w17w210w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb7ce83b1…2c96
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xf7ba1e5d…b56b
0x34b655…2a6f
4 touches
1 conflict
0x186d8c65…9121
0x34b655…2a6f
4 touches
1 conflict
0x31792d70…b868
0x81a224…7777
2 touches
1 conflict
0x78375f3b…b4cc
0x34b655…2a6f
2 touches
0 conflicts
0x9b675cde…5645
0x34b655…2a6f
2 touches
0 conflicts
0xbfca3cd0…5023
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0xb7ce83b1b6…352c96
Audit this contract →
← previous block·next block →recent activity