← previous blocknext block →recent activity
Analyzing
Block #106,943,973
17 transactions · 17 stateful · 2026-09-22 04:49:04 UTC
Parallelism
59/100
Blocked
47%
Avg conflicts / tx
1.18
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,943,973 · 17 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w27w38w411w313w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8519ae5c…993e
0x34b655…2a6f
10 touches
10 conflicts
0x6c26d635…1bbf
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd9a74048…63af
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0xd125c3f8…99aa
0x34b655…2a6f
6 touches
3 conflicts
0x12e77486…ec2b
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
10 conflicts on slot 0x8519ae5c0f…2a993e
Audit this contract →
← previous block·next block →recent activity