← previous blocknext block →recent activity
Analyzing
Block #106,932,447
20 transactions · 18 stateful · 2026-09-22 03:51:03 UTC
Parallelism
75/100
Blocked
33%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,932,447 · 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
1w02w13w05w06w18w19w218w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2d2f78de…4ce5
0x34b655…2a6f
10 touches
10 conflicts
0x4786839b…c29a
0x34b655…2a6f
8 touches
6 conflicts
0x4ebd9eec…d5c3
0x34b655…2a6f
6 touches
3 conflicts
0x810a3aa2…0227
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002d
0x1b6862…e19c
4 touches
1 conflict
0xada193dc…5c7e
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x36d207d1…97e0
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 0x2d2f78dec9…044ce5
Audit this contract →
← previous block·next block →recent activity