← previous blocknext block →recent activity
Analyzing
Block #99,701,517
19 transactions · 19 stateful · 2026-08-27 19:52:34 UTC
Parallelism
63/100
Blocked
37%
Avg conflicts / tx
1.11
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,701,517 · 19 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
1w03w04w15w26w38w312w417w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdad20621…06b1
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xf65a7a7b…532c
0x34b655…2a6f
8 touches
6 conflicts
0x57e5abc1…286f
0x34b655…2a6f
6 touches
3 conflicts
0x775a8ad3…8307
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xa78ae601…71e2
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
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
10 conflicts on slot 0xdad20621a2…0306b1
Audit this contract →
← previous block·next block →recent activity