← previous blocknext block →recent activity
Analyzing
Block #106,809,561
24 transactions · 22 stateful · 2026-09-21 17:32:31 UTC
Parallelism
79/100
Blocked
45%
Avg conflicts / tx
0.92
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,809,561 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w010w011w012w213w114w115w216w117w218w321w223w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01f19c33…170d
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x51087f5a…61f7
0x34b655…2a6f
8 touches
6 conflicts
0xa1146bac…9fa8
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd192f4ed…d7ec
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x01f19c3396…f1170d
Audit this contract →
← previous block·next block →recent activity