← previous blocknext block →recent activity
Analyzing
Block #98,733,287
21 transactions · 19 stateful · 2026-08-24 10:24:27 UTC
Parallelism
81/100
Blocked
58%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,733,287 · 21 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
2w03w15w06w17w28w09w110w212w013w114w215w317w319w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1bbb92cc…fe1d
0x40c49f…2af0
8 touches
6 conflicts
0x6518075e…2b17
0x2a68ba…90c5
8 touches
6 conflicts
0x2b54cadb…4425
0xd18b7e…414b
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x7de57974…f5ba
0x34b655…2a6f
6 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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: 0x40c49f17…d22af0
6 conflicts on slot 0x1bbb92cc3e…a6fe1d
Audit this contract →
← previous block·next block →recent activity