← previous blocknext block →recent activity
Analyzing
Block #98,426,344
18 transactions · 18 stateful · 2026-08-23 08:03:59 UTC
Parallelism
67/100
Blocked
39%
Avg conflicts / tx
0.72
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,426,344 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w28w110w311w412w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x58799a46…7030
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x788e2096…c37f
0x34b655…2a6f
6 touches
3 conflicts
0x7de57974…f5ba
0x34b655…2a6f
6 touches
3 conflicts
0x88f8f168…e05a
0x34b655…2a6f
6 touches
3 conflicts
0xa5a387a4…3b68
0x34b655…2a6f
6 touches
3 conflicts
0xaae6463e…bfcc
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 0x58799a469e…b57030
Audit this contract →
← previous block·next block →recent activity