← previous blocknext block →recent activity
Analyzing
Block #106,800,949
21 transactions · 21 stateful · 2026-09-21 16:49:10 UTC
Parallelism
67/100
Blocked
52%
Avg conflicts / tx
1.62
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,800,949 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w06w17w29w110w212w314w415w116w217w518w620w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52f57971…c16b
0x34b655…2a6f
14 touches
21 conflicts
0x9edb7ad7…8d56
0x34b655…2a6f
14 touches
21 conflicts
0xe460355e…6845
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x629f79db…ed1e
0x34b655…2a6f
6 touches
3 conflicts
0x69411fb3…e36d
0x34b655…2a6f
6 touches
3 conflicts
0xa6464996…3af9
0x34b655…2a6f
6 touches
3 conflicts
0xc389d1ff…6a00
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
21 conflicts on slot 0x52f579712a…efc16b
Audit this contract →
← previous block·next block →recent activity