← previous blocknext block →recent activity
Analyzing
Block #99,092,311
10 transactions · 10 stateful · 2026-08-25 16:37:40 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,092,311 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x62910921…3016
0x34b655…2a6f
4 touches
1 conflict
0x140223cf…9ccc
0x34b655…2a6f
2 touches
0 conflicts
0x1c2f0c4c…9bca
0x34b655…2a6f
2 touches
0 conflicts
0x295780b7…d2d1
0x34b655…2a6f
2 touches
0 conflicts
0x2cb63fe0…626e
0x34b655…2a6f
2 touches
0 conflicts
0x3d1a888b…ba9d
0x34b655…2a6f
2 touches
0 conflicts
0x4aba2895…e93e
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity