← previous blocknext block →recent activity
Analyzing
Block #106,801,960
16 transactions · 16 stateful · 2026-09-21 16:54:15 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,801,960 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w17w28w311w112w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x81a84ef1…6e1b
0x34b655…2a6f
10 touches
10 conflicts
0x3cf50d44…961b
0x34b655…2a6f
8 touches
6 conflicts
0xabf57eb6…416d
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001a
0x1b6862…e19c
6 touches
3 conflicts
0xcb45d9d6…cb82
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x1e6832ca…0340
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
10 conflicts on slot 0x81a84ef1e5…ea6e1b
Audit this contract →
← previous block·next block →recent activity