← previous blocknext block →recent activity
Analyzing
Block #106,533,570
24 transactions · 21 stateful · 2026-09-20 18:22:28 UTC
Parallelism
67/100
Blocked
57%
Avg conflicts / tx
1.38
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,533,570 · 24 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
1w03w04w15w17w08w09w111w114w215w316w417w518w619w723w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xd41f5136…97c6
0x34b655…2a6f
10 touches
10 conflicts
0xf2acfba1…5e29
0x34b655…2a6f
10 touches
10 conflicts
0x23769ebc…c8ed
0x34b655…2a6f
8 touches
6 conflicts
0x21af3bbf…9d0c
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0xba1edffb…323e
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity