← previous blocknext block →recent activity
Analyzing
Block #98,916,030
35 transactions · 31 stateful · 2026-08-25 01:44:10 UTC
Parallelism
89/100
Blocked
32%
Avg conflicts / tx
0.51
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,916,030 · 35 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w07w08w09w110w011w112w215w119w020w121w222w124w232w234w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc95f91db…a901
0x34b655…2a6f
6 touches
3 conflicts
0x7de57974…f5ba
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x2a354a63…0515
0x065c9d…c394
6 touches
3 conflicts
0xa5a387a4…3b68
0x34b655…2a6f
5 touches
3 conflicts
0x5b09bf44…5907
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 0xc95f91db39…24a901
Audit this contract →
← previous block·next block →recent activity