← previous blocknext block →recent activity
Analyzing
Block #98,495,375
21 transactions · 20 stateful · 2026-08-23 13:51:38 UTC
Parallelism
76/100
Blocked
40%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,495,375 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w05w16w010w111w212w013w314w416w017w118w220w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9d9f3717…44e7
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xbbee74c2…567a
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xa2813094…18b3
0x065c9d…c394
4 touches
1 conflict
0xb30f077a…1c26
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 0x9d9f371782…a844e7
Audit this contract →
← previous block·next block →recent activity