← previous blocknext block →recent activity
Analyzing
Block #98,766,987
23 transactions · 21 stateful · 2026-08-24 13:14:07 UTC
Parallelism
74/100
Blocked
38%
Avg conflicts / tx
0.78
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,766,987 · 23 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
1w02w13w17w013w014w218w119w220w321w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x62910921…3016
0x34b655…2a6f
6 touches
3 conflicts
0x2f19104d…4a75
0xd32edf…ff58
5 touches
3 conflicts
0x4635fb46…4cfd
0x34b655…2a6f
4 touches
1 conflict
0x6fbc2e5a…e69c
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity