← previous blocknext block →recent activity
Analyzing
Block #106,923,953
22 transactions · 20 stateful · 2026-09-22 03:08:18 UTC
Parallelism
64/100
Blocked
60%
Avg conflicts / tx
1.77
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,923,953 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w28w29w311w412w215w116w517w618w720w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b5840c7…1e67
0x34b655…2a6f
16 touches
28 conflicts
0xea2d1275…76c8
0x34b655…2a6f
12 touches
15 conflicts
0xdf64e5e6…75e8
0x34b655…2a6f
10 touches
10 conflicts
0x46483cb1…e7ca
0x34b655…2a6f
8 touches
6 conflicts
0x53ca1284…cb2c
0x34b655…2a6f
8 touches
6 conflicts
0x523a970e…97c0
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0xacd9c381…91d1
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
28 conflicts on slot 0x2b5840c773…ed1e67
Audit this contract →
← previous block·next block →recent activity