← previous blocknext block →recent activity
Analyzing
Block #98,382,771
13 transactions · 13 stateful · 2026-08-23 04:24:45 UTC
Parallelism
77/100
Blocked
23%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,382,771 · 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
2w06w07w18w212w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6254804c…a03b
0x34b655…2a6f
4 touches
1 conflict
0x6254804c…a03c
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x44e37ad2…d6ef
0x34b655…2a6f
4 touches
1 conflict
0x969295c6…6d07
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
2 touches
0 conflicts
0xd6113c0f…0a4b
0x34b655…2a6f
2 touches
0 conflicts
0xe283e878…7262
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
1 conflict on slot 0x6254804ca4…efa03b
Audit this contract →
← previous block·next block →recent activity