← previous blocknext block →recent activity
Analyzing
Block #99,616,316
23 transactions · 21 stateful · 2026-08-27 12:41:20 UTC
Parallelism
78/100
Blocked
24%
Avg conflicts / tx
0.52
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,616,316 · 23 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
1w04w05w17w08w112w215w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x354d79bd…2bec
0x34b655…2a6f
8 touches
6 conflicts
0x6fce7a05…d778
0x34b655…2a6f
8 touches
6 conflicts
0x939cdd56…00c8
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xf0996b9c…abd4
0x34b655…2a6f
4 touches
1 conflict
0x2b376893…27a7
0x34b655…2a6f
4 touches
1 conflict
0x3e49348b…9445
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity