← previous blocknext block →recent activity
Analyzing
Block #99,869,305
11 transactions · 11 stateful · 2026-08-28 10:01:51 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.82
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,869,305 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w28w39w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb856d1a1…1f18
0x34b655…2a6f
8 touches
6 conflicts
0x16993363…919c
0x34b655…2a6f
8 touches
6 conflicts
0xca608d0c…f23b
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xfc24540b…6463
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0fd02b10…97c5
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 0xb856d1a127…bf1f18
Audit this contract →
← previous block·next block →recent activity