← previous blocknext block →recent activity
Analyzing
Block #106,953,103
24 transactions · 24 stateful · 2026-09-22 05:35:02 UTC
Parallelism
75/100
Blocked
42%
Avg conflicts / tx
0.92
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,953,103 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w17w08w19w010w211w312w415w017w118w119w522w023w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c7c9c27…626f
0x34b655…2a6f
10 touches
10 conflicts
0x8d5fc820…1750
0x34b655…2a6f
10 touches
10 conflicts
0x8f18c248…9da5
0x34b655…2a6f
6 touches
3 conflicts
0x4e58deff…c5d0
0x34b655…2a6f
6 touches
3 conflicts
0x33303721…96ed
0x34b655…2a6f
4 touches
1 conflict
0x3d4ceda4…84c4
0x34b655…2a6f
4 touches
1 conflict
0x49b9fdd5…9c16
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
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 0x4c7c9c2712…f9626f
Audit this contract →
← previous block·next block →recent activity