← previous blocknext block →recent activity
Analyzing
Block #106,397,223
22 transactions · 21 stateful · 2026-09-20 06:56:12 UTC
Parallelism
68/100
Blocked
43%
Avg conflicts / tx
0.82
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,397,223 · 22 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
1w02w110w213w014w115w216w318w319w420w521w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x1d73a8e0…374e
0x5be4ee…673f
7 touches
6 conflicts
0x1d73a8e0…3740
0x5be4ee…673f
7 touches
6 conflicts
0x5060cdde…445d
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x25db999f…f707
0x34b655…2a6f
4 touches
1 conflict
0x558eafff…804d
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity