← previous blocknext block →recent activity
Analyzing
Block #99,163,361
14 transactions · 12 stateful · 2026-08-25 22:35:15 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,163,361 · 14 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
1w02w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee75c266…f8c6
0x34b655…2a6f
4 touches
1 conflict
0x6bce5317…a995
0x34b655…2a6f
4 touches
1 conflict
0x6f8b34e2…5357
0x34b655…2a6f
4 touches
1 conflict
0x72b221b7…d89b
0x34b655…2a6f
4 touches
1 conflict
0x826cce18…251c
0x34b655…2a6f
4 touches
1 conflict
0x94710b77…a921
0x34b655…2a6f
4 touches
1 conflict
0xaae6463e…bfcc
0x34b655…2a6f
4 touches
1 conflict
0xaf498679…7732
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
1 conflict on slot 0xee75c26607…24f8c6
Audit this contract →
← previous block·next block →recent activity