← previous blocknext block →recent activity
Analyzing
Block #106,435,300
25 transactions · 24 stateful · 2026-09-20 10:07:50 UTC
Parallelism
80/100
Blocked
42%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,435,300 · 25 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
1w02w13w24w05w36w210w011w114w015w116w319w020w121w423w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbaf6ed88…c179
0x34b655…2a6f
6 touches
3 conflicts
0xc71de274…0c33
0x34b655…2a6f
6 touches
3 conflicts
0x65b12d95…0991
0x34b655…2a6f
6 touches
3 conflicts
0xc96ccb33…491f
0x34b655…2a6f
6 touches
3 conflicts
0xd563f3a1…94b1
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x0de7749d…5bef
0x34b655…2a6f
6 touches
3 conflicts
0x5906754f…b584
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
3 conflicts on slot 0xbaf6ed88a9…dec179
Audit this contract →
← previous block·next block →recent activity