← previous blocknext block →recent activity
Analyzing
Block #98,287,021
16 transactions · 16 stateful · 2026-08-22 20:23:00 UTC
Parallelism
81/100
Blocked
31%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,287,021 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w07w08w19w010w111w214w215w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2c7ff81…8bfd
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xecea23db…7fb9
0x34b655…2a6f
6 touches
3 conflicts
0x1867b653…e61b
0x34b655…2a6f
4 touches
1 conflict
0x3243acff…7af3
0x34b655…2a6f
4 touches
1 conflict
0x33fb9b62…d0c3
0x34b655…2a6f
4 touches
1 conflict
0x42e5184f…4e8b
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0xe2c7ff815d…698bfd
Audit this contract →
← previous block·next block →recent activity