← previous blocknext block →recent activity
Analyzing
Block #98,741,873
26 transactions · 24 stateful · 2026-08-24 11:07:39 UTC
Parallelism
81/100
Blocked
50%
Avg conflicts / tx
0.96
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,741,873 · 26 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
1w02w13w24w36w07w08w110w011w012w113w114w015w116w219w320w021w222w425w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x76622fb2…4f08
0x34b655…2a6f
8 touches
6 conflicts
0xfe0e60bc…0b56
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0019
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0029
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xe01158fd…f97d
0x1b6862…e19c
6 touches
3 conflicts
0x4a270745…5cc9
0x34b655…2a6f
6 touches
3 conflicts
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
6 conflicts on slot 0x76622fb2e3…024f08
Audit this contract →
← previous block·next block →recent activity