← previous blocknext block →recent activity
Analyzing
Block #106,955,764
21 transactions · 21 stateful · 2026-09-22 05:48:25 UTC
Parallelism
71/100
Blocked
43%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,955,764 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w17w08w09w110w111w214w315w116w418w019w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a58c7c0…07dc
0x34b655…2a6f
8 touches
6 conflicts
0xab981df1…2941
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x1a0a5278…9369
0x34b655…2a6f
6 touches
3 conflicts
0x49a18632…422e
0x34b655…2a6f
4 touches
1 conflict
0x4ec9ff52…e6f7
0x34b655…2a6f
4 touches
1 conflict
0x71ecf7c5…8b1e
0x34b655…2a6f
4 touches
1 conflict
0x9375a764…dca1
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
6 conflicts on slot 0x9a58c7c02c…c007dc
Audit this contract →
← previous block·next block →recent activity