← previous blocknext block →recent activity
Analyzing
Block #98,594,419
25 transactions · 25 stateful · 2026-08-23 22:27:41 UTC
Parallelism
68/100
Blocked
32%
Avg conflicts / tx
1.28
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #98,594,419 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w26w37w412w514w623w424w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x6d5c5d72…914b
0x34b655…2a6f
6 touches
3 conflicts
0xdb3eb062…05e3
0x34b655…2a6f
6 touches
3 conflicts
0xb482658a…e4f5
0x34b655…2a6f
6 touches
3 conflicts
0x5e2ea201…12de
0x34b655…2a6f
6 touches
3 conflicts
0x98834cc0…6c23
0x34b655…2a6f
4 touches
1 conflict
0x9c623cfd…b42b
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
28 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity