← previous blocknext block →recent activity
Analyzing
Block #98,435,143
29 transactions · 26 stateful · 2026-08-23 08:48:15 UTC
Parallelism
83/100
Blocked
27%
Avg conflicts / tx
0.66
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,435,143 · 29 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w09w011w112w216w017w121w322w024w025w426w427w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x73726971…36e9
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x6f132c01…cdcc
0x34b655…2a6f
6 touches
3 conflicts
0x6b595a5d…894c
0x34b655…2a6f
4 touches
1 conflict
0x850148cf…4981
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f1
0x34b655…2a6f
4 touches
1 conflict
0xa38c430a…e3cb
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
10 conflicts on slot 0x7372697137…9b36e9
Audit this contract →
← previous block·next block →recent activity