← previous blocknext block →recent activity
Analyzing
Block #106,923,533
21 transactions · 21 stateful · 2026-09-22 03:06:11 UTC
Parallelism
52/100
Blocked
57%
Avg conflicts / tx
1.76
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,923,533 · 21 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w28w39w410w111w512w613w714w815w919w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x85bfd0af…ce96
0x34b655…2a6f
14 touches
21 conflicts
0x46483cb1…e7ca
0x34b655…2a6f
12 touches
15 conflicts
0xccebf5c5…8758
0x34b655…2a6f
12 touches
15 conflicts
0xc7cbc5e5…e7d7
0x34b655…2a6f
12 touches
15 conflicts
0xb3d828cf…a9b8
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…001d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002d
0x1b6862…e19c
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
21 conflicts on slot 0x85bfd0afba…f5ce96
Audit this contract →
← previous block·next block →recent activity