← previous blocknext block →recent activity
Analyzing
Block #99,856,012
22 transactions · 20 stateful · 2026-08-28 08:54:49 UTC
Parallelism
64/100
Blocked
55%
Avg conflicts / tx
1.32
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #99,856,012 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w38w09w113w214w315w417w518w619w420w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdb8288e3…7979
0x34b655…2a6f
14 touches
21 conflicts
0xcdbcbb1e…b5d2
0x34b655…2a6f
8 touches
6 conflicts
0x99f41a48…e98d
0x34b655…2a6f
8 touches
6 conflicts
0xe8bcb025…27b8
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0028
0x1b6862…e19c
6 touches
3 conflicts
0x3a3097d7…2ab2
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 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
21 conflicts on slot 0xdb8288e38f…6f7979
Audit this contract →
← previous block·next block →recent activity