← previous blocknext block →recent activity
Analyzing
Block #98,456,091
17 transactions · 15 stateful · 2026-08-23 10:33:46 UTC
Parallelism
65/100
Blocked
40%
Avg conflicts / tx
0.76
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,456,091 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w08w19w210w212w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xa7ecbbe7…f713
0x34b655…2a6f
8 touches
6 conflicts
0x48132b64…8e95
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xd9920319…36f5
0x34b655…2a6f
4 touches
1 conflict
0x0c396575…8af6
0x34b655…2a6f
4 touches
1 conflict
0x2130a548…c1de
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
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
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity