← previous blocknext block →recent activity
Analyzing
Block #106,357,258
20 transactions · 19 stateful · 2026-09-20 03:35:04 UTC
Parallelism
60/100
Blocked
47%
Avg conflicts / tx
0.9
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,357,258 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w27w38w49w213w014w115w518w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
10 touches
10 conflicts
0xc8f755b6…7b04
0x34b655…2a6f
6 touches
3 conflicts
0xd563f3a1…94b1
0x34b655…2a6f
6 touches
3 conflicts
0x2533fe3f…344d
0x34b655…2a6f
4 touches
1 conflict
0x25bd380f…a658
0x34b655…2a6f
4 touches
1 conflict
0x3380282c…cf3c
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
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 0xb3fb9fb561…7664db
Audit this contract →
← previous block·next block →recent activity