← previous blocknext block →recent activity
Analyzing
Block #106,456,821
24 transactions · 22 stateful · 2026-09-20 11:56:12 UTC
Parallelism
63/100
Blocked
64%
Avg conflicts / tx
1.92
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,456,821 · 24 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w311w112w213w314w416w417w518w519w620w721w823w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2aab0897…78f7
0x34b655…2a6f
18 touches
36 conflicts
0xb6c3be06…1644
0x34b655…2a6f
18 touches
36 conflicts
0xb9b077a8…e029
0x34b655…2a6f
16 touches
28 conflicts
0xa3ed5a09…c6d3
0x34b655…2a6f
10 touches
10 conflicts
0x7462b8f2…6312
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…002c
0x1b6862…e19c
8 touches
6 conflicts
0xd18a8dca…452d
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 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
36 conflicts on slot 0x2aab08973a…f178f7
Audit this contract →
← previous block·next block →recent activity