← previous blocknext block →recent activity
Analyzing
Block #106,435,952
24 transactions · 20 stateful · 2026-09-20 10:11:07 UTC
Parallelism
79/100
Blocked
40%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,435,952 · 24 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
1w02w13w05w06w112w113w216w119w220w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd563f3a1…94b1
0x34b655…2a6f
10 touches
10 conflicts
0x4b1ed7eb…9ec1
0x34b655…2a6f
6 touches
3 conflicts
0xc71de274…0c33
0x34b655…2a6f
6 touches
3 conflicts
0x2d071de0…c86e
0x34b655…2a6f
4 touches
1 conflict
0x31d88d27…7617
0x34b655…2a6f
4 touches
1 conflict
0x375df097…cfd4
0x34b655…2a6f
4 touches
1 conflict
0x3fa1fac4…826c
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
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 0xd563f3a18c…f494b1
Audit this contract →
← previous block·next block →recent activity