← previous blocknext block →recent activity
Analyzing
Block #98,523,618
27 transactions · 27 stateful · 2026-08-23 16:18:27 UTC
Parallelism
78/100
Blocked
41%
Avg conflicts / tx
0.96
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,523,618 · 27 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w17w09w110w211w212w314w215w316w421w525w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xa3250389…8774
0x34b655…2a6f
8 touches
6 conflicts
0x67291160…cdf4
0x34b655…2a6f
8 touches
6 conflicts
0xaf30c163…0fb6
0x34b655…2a6f
8 touches
6 conflicts
0x5d6da397…6c5c
0x34b655…2a6f
8 touches
6 conflicts
0xfaeefeb3…889f
0x34b655…2a6f
6 touches
3 conflicts
0xb544c2f4…5fe4
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
15 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity