← previous blocknext block →recent activity
Analyzing
Block #98,062,691
26 transactions · 22 stateful · 2026-08-22 01:33:39 UTC
Parallelism
88/100
Blocked
36%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,062,691 · 26 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
1w02w03w16w09w010w114w015w117w018w119w020w121w223w225w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5fd0a899…4747
0x34b655…2a6f
6 touches
3 conflicts
0x03e5b578…2fec
0xa6afd3…d132
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xf90c6521…d8f0
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xc26c0c87…c857
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0002
0xbb3f3c…e046
4 touches
1 conflict
0x47be2b16…7c11
0x34b655…2a6f
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 0x5fd0a89935…ac4747
Audit this contract →
← previous block·next block →recent activity