← previous blocknext block →recent activity
Analyzing
Block #98,460,135
13 transactions · 11 stateful · 2026-08-23 10:54:13 UTC
Parallelism
77/100
Blocked
36%
Avg conflicts / tx
0.54
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,460,135 · 13 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
3w04w05w16w210w011w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x41755291…977f
0x065c9d…c394
4 touches
1 conflict
0x47b807a2…3307
0x065c9d…c394
4 touches
1 conflict
0x514fa990…f462
0x34b655…2a6f
4 touches
1 conflict
0x2d94ecd9…43db
0x34b655…2a6f
2 touches
0 conflicts
0x5498e344…6326
0x34b655…2a6f
2 touches
0 conflicts
0x7aad02c6…b979
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity