← previous blocknext block →recent activity
Analyzing
Block #106,381,603
35 transactions · 35 stateful · 2026-09-20 05:37:35 UTC
Parallelism
69/100
Blocked
57%
Avg conflicts / tx
2.17
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,381,603 · 35 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w06w111w217w119w120w322w223w424w525w626w727w828w929w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc96ccb33…491f
0x34b655…2a6f
18 touches
36 conflicts
0x4d091c36…3028
0x34b655…2a6f
10 touches
10 conflicts
0x1b25f260…c429
0x34b655…2a6f
10 touches
10 conflicts
0x0262e1c6…52e1
0x34b655…2a6f
10 touches
10 conflicts
0xe8058ec4…ebac
0x34b655…2a6f
8 touches
6 conflicts
0x56e56687…1766
0x34b655…2a6f
8 touches
6 conflicts
0x3ca268be…8865
0x34b655…2a6f
8 touches
6 conflicts
0xdd77da90…6df4
0x34b655…2a6f
8 touches
6 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
36 conflicts on slot 0xc96ccb3323…c9491f
Audit this contract →
← previous block·next block →recent activity