← previous blocknext block →recent activity
Analyzing
Block #98,391,648
22 transactions · 20 stateful · 2026-08-23 05:09:25 UTC
Parallelism
86/100
Blocked
40%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,391,648 · 22 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
1w02w03w14w25w06w09w011w113w115w216w018w119w121w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7de57974…f5ba
0x34b655…2a6f
6 touches
3 conflicts
0xe5398625…3e9c
0x34b655…2a6f
5 touches
3 conflicts
0x15b3ea9f…ef46
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…1266
0x34b655…2a6f
4 touches
1 conflict
0xde5c131f…da2c
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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
3 conflicts on slot 0x7de579746e…f0f5ba
Audit this contract →
← previous block·next block →recent activity