← previous blocknext block →recent activity
Analyzing
Block #98,062,917
20 transactions · 15 stateful · 2026-08-22 01:34:47 UTC
Parallelism
75/100
Blocked
47%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,062,917 · 20 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
1w03w16w07w011w212w213w314w015w117w419w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc0a73ae2…2e95
0x34b655…2a6f
6 touches
3 conflicts
0x8116f058…4827
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c3
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0007
0x340143…768f
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 0xc0a73ae2a1…182e95
Audit this contract →
← previous block·next block →recent activity