← previous blocknext block →recent activity
Analyzing
Block #98,069,693
24 transactions · 22 stateful · 2026-08-22 02:08:53 UTC
Parallelism
92/100
Blocked
32%
Avg conflicts / tx
0.38
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,069,693 · 24 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w05w111w012w113w115w116w017w118w019w123w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe90c1bfa…8b5b
0x34b655…2a6f
4 touches
1 conflict
0x53eac009…b61b
0x34b655…2a6f
4 touches
1 conflict
0x736b9166…5ea5
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5e8
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
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
1 conflict on slot 0xe90c1bfa79…348b5b
Audit this contract →
← previous block·next block →recent activity