← previous blocknext block →recent activity
Analyzing
Block #106,252,829
21 transactions · 21 stateful · 2026-09-19 18:49:34 UTC
Parallelism
62/100
Blocked
52%
Avg conflicts / tx
1.48
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,252,829 · 21 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
1w02w13w24w35w08w19w212w314w415w516w617w720w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba73be23…c570
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
8 touches
6 conflicts
0xa3ed5a09…c6d3
0x34b655…2a6f
8 touches
6 conflicts
0xba5743c7…21c6
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
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
21 conflicts on slot 0xba73be23ce…3fc570
Audit this contract →
← previous block·next block →recent activity