← previous blocknext block →recent activity
Analyzing
Block #98,502,162
24 transactions · 23 stateful · 2026-08-23 14:26:23 UTC
Parallelism
75/100
Blocked
52%
Avg conflicts / tx
1.21
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,502,162 · 24 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
1w05w16w27w38w010w112w113w214w315w216w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x627738d1…db02
0x34b655…2a6f
8 touches
6 conflicts
0x5c8a8db2…8a6d
0x34b655…2a6f
8 touches
6 conflicts
0xa366dc41…b2d8
0xa6afd3…d132
6 touches
3 conflicts
0xafb519c4…cba0
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity