← previous blocknext block →recent activity
Analyzing
Block #98,064,617
25 transactions · 19 stateful · 2026-08-22 01:43:21 UTC
Parallelism
84/100
Blocked
47%
Avg conflicts / tx
0.52
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,064,617 · 25 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
1w02w03w15w06w08w19w210w312w013w115w116w123w324w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9fc6ea79…e2dc
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x2b69cc9b…2aca
0x34b655…2a6f
4 touches
1 conflict
0x47be2b16…7c11
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x49299fcf…c552
0x34b655…2a6f
4 touches
1 conflict
0x4d2a24c9…b564
0x34b655…2a6f
4 touches
1 conflict
0x5fd61b3c…628d
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
3 conflicts on slot 0x9fc6ea791d…ace2dc
Audit this contract →
← previous block·next block →recent activity