← previous blocknext block →recent activity
Analyzing
Block #106,921,493
23 transactions · 23 stateful · 2026-09-22 02:55:55 UTC
Parallelism
52/100
Blocked
57%
Avg conflicts / tx
2.17
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,921,493 · 23 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
1w04w05w16w27w38w49w210w511w612w713w814w915w1018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x206f4379…e08a
0x34b655…2a6f
18 touches
36 conflicts
0xccebf5c5…8758
0x34b655…2a6f
14 touches
21 conflicts
0x799c3770…96ae
0x34b655…2a6f
14 touches
21 conflicts
0xab981df1…2941
0x34b655…2a6f
12 touches
15 conflicts
0xa66499c2…9f47
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0xe4a10d60…841b
0x34b655…2a6f
6 touches
3 conflicts
0x7fc8f46e…0f75
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
36 conflicts on slot 0x206f43799d…55e08a
Audit this contract →
← previous block·next block →recent activity