← previous blocknext block →recent activity
Analyzing
Block #99,710,836
30 transactions · 26 stateful · 2026-08-27 20:39:38 UTC
Parallelism
83/100
Blocked
35%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,710,836 · 30 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w09w010w113w014w115w216w318w424w025w126w227w028w129w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x733c7779…a647
0x34b655…2a6f
8 touches
6 conflicts
0xadce6355…03bf
0xa6afd3…d132
8 touches
6 conflicts
0x3ad04ce1…1904
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0x21e8ab54…3b4b
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x72ac5a55…9bf6
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
6 conflicts on slot 0x733c7779fd…f4a647
Audit this contract →
← previous block·next block →recent activity