← previous blocknext block →recent activity
Analyzing
Block #98,067,619
36 transactions · 31 stateful · 2026-08-22 01:58:27 UTC
Parallelism
89/100
Blocked
35%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,067,619 · 36 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
2w03w04w05w16w210w011w116w117w219w021w122w224w328w029w132w033w135w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa5ab7310…4950
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x5c1b956d…14d3
0x34b655…2a6f
6 touches
3 conflicts
0x8db32935…81a7
0x34b655…2a6f
6 touches
3 conflicts
0xe11d2f5e…8488
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
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
6 conflicts on slot 0xa5ab73100e…d34950
Audit this contract →
← previous block·next block →recent activity