← previous blocknext block →recent activity
Analyzing
Block #106,915,777
47 transactions · 46 stateful · 2026-09-22 02:27:09 UTC
Parallelism
70/100
Blocked
50%
Avg conflicts / tx
2.17
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #106,915,777 · 47 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w09w010w111w212w313w414w515w616w717w818w919w120w221w322w423w1024w1125w1226w1327w145w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa9988419…9f45
0x34b655…2a6f
22 touches
55 conflicts
0xe9c8c872…e38c
0x34b655…2a6f
20 touches
45 conflicts
0x42522e76…2592
0x34b655…2a6f
20 touches
45 conflicts
0xcc844ab5…4c6d
0x34b655…2a6f
18 touches
36 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
16 touches
28 conflicts
0xedfd12b0…dba4
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x5c2df7aa…8f80
0x34b655…2a6f
6 touches
3 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
55 conflicts on slot 0xa998841984…609f45
Audit this contract →
← previous block·next block →recent activity