← previous blocknext block →recent activity
Analyzing
Block #99,076,276
18 transactions · 18 stateful · 2026-08-25 15:16:40 UTC
Parallelism
61/100
Blocked
50%
Avg conflicts / tx
0.94
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,076,276 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w06w18w011w113w214w315w416w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x3ed49969…0ed7
0x34b655…2a6f
7 touches
6 conflicts
0xa02838a3…bc54
0x34b655…2a6f
6 touches
3 conflicts
0x070a562a…8147
0x34b655…2a6f
5 touches
3 conflicts
0xfe3d37ee…6e67
0x34b655…2a6f
4 touches
1 conflict
0xff324643…41db
0x34b655…2a6f
4 touches
1 conflict
0xeaced15b…2221
0x754704…b603
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