← previous blocknext block →recent activity
Analyzing
Block #106,413,311
19 transactions · 18 stateful · 2026-09-20 08:17:10 UTC
Parallelism
68/100
Blocked
33%
Avg conflicts / tx
0.84
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,413,311 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w511w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9b7187dd…3085
0x34b655…2a6f
12 touches
15 conflicts
0xfdd131fa…dbdb
0x34b655…2a6f
12 touches
15 conflicts
0x74e46435…fdcd
0x34b655…2a6f
8 touches
6 conflicts
0x3fa1fac4…826c
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0xdcf021b9…11db
0x34b655…2a6f
6 touches
3 conflicts
0xa1524d24…57bc
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
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
15 conflicts on slot 0x9b7187dd36…6b3085
Audit this contract →
← previous block·next block →recent activity