← previous blocknext block →recent activity
Analyzing
Block #98,424,081
21 transactions · 17 stateful · 2026-08-23 07:52:36 UTC
Parallelism
86/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,424,081 · 21 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
4w05w18w011w012w013w114w115w220w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc9cc8fde…abfa
0x34b655…2a6f
6 touches
3 conflicts
0x42e5184f…4e8b
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x24b08f9c…e594
0x34b655…2a6f
6 touches
3 conflicts
0xd33c2ab5…ccc3
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x176c3dde…df92
0x34b655…2a6f
5 touches
3 conflicts
0xa9988419…9f45
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 0xc9cc8fde5e…51abfa
Audit this contract →
← previous block·next block →recent activity