← previous blocknext block →recent activity
Analyzing
Block #106,282,532
24 transactions · 23 stateful · 2026-09-19 21:19:02 UTC
Parallelism
79/100
Blocked
52%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,282,532 · 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
1w02w03w05w06w18w211w113w014w115w217w118w119w220w321w322w123w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfac38cc8…fb9d
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x5c3ecb74…af1d
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x18cf3003…51d1
0x065c9d…c394
6 touches
3 conflicts
0x88fc2529…3f0d
0xa6afd3…d132
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0xfac38cc8b7…a4fb9d
Audit this contract →
← previous block·next block →recent activity