← previous blocknext block →recent activity
Analyzing
Block #98,086,429
24 transactions · 19 stateful · 2026-08-22 03:33:07 UTC
Parallelism
83/100
Blocked
42%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,086,429 · 24 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
2w04w05w16w29w010w112w114w217w318w323w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53eac009…b61b
0x34b655…2a6f
6 touches
3 conflicts
0x2bd1c200…56de
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x3db5de65…30f3
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x58620f29…db5a
0x34b655…2a6f
4 touches
1 conflict
0x6a2ca7be…18a8
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 0x53eac00933…f3b61b
Audit this contract →
← previous block·next block →recent activity