← previous blocknext block →recent activity
Analyzing
Block #98,082,232
13 transactions · 13 stateful · 2026-08-22 03:12:00 UTC
Parallelism
77/100
Blocked
38%
Avg conflicts / tx
0.69
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,082,232 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w06w17w19w210w011w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xb575cf74…fbd5
0x34b655…2a6f
6 touches
3 conflicts
0x9aa7036b…a2a7
0xa6afd3…d132
6 touches
3 conflicts
0x10d80fee…dbda
0x2b46c0…1669
4 touches
1 conflict
0x40970e69…da50
0x2b46c0…1669
4 touches
1 conflict
0x8cf3d245…1d0d
0x2b46c0…1669
4 touches
1 conflict
0xb05cd4f5…73d0
0x2b46c0…1669
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity