← previous blocknext block →recent activity
Analyzing
Block #106,419,768
13 transactions · 13 stateful · 2026-09-20 08:49:40 UTC
Parallelism
54/100
Blocked
54%
Avg conflicts / tx
1.54
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,419,768 · 13 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
1w02w14w25w06w17w28w39w410w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22fc5161…e258
0x34b655…2a6f
12 touches
15 conflicts
0x8c6f8a15…2930
0x34b655…2a6f
10 touches
10 conflicts
0x5e1c23e9…4f81
0x34b655…2a6f
10 touches
10 conflicts
0x54f7f60f…43cc
0x34b655…2a6f
8 touches
6 conflicts
0x3cb7ee74…b8a5
0x34b655…2a6f
6 touches
3 conflicts
0xb9b077a8…e029
0x34b655…2a6f
6 touches
3 conflicts
0xecd87a39…d9c5
0x34b655…2a6f
4 touches
1 conflict
0x1b25f260…c429
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
15 conflicts on slot 0x22fc516177…b0e258
Audit this contract →
← previous block·next block →recent activity