← previous blocknext block →recent activity
Analyzing
Block #99,668,170
35 transactions · 28 stateful · 2026-08-27 17:03:27 UTC
Parallelism
83/100
Blocked
39%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,668,170 · 35 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w08w09w310w112w413w517w118w219w126w327w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e1c23e9…4f81
0x34b655…2a6f
10 touches
10 conflicts
0x31c4594c…ede7
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xbcb11536…450f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0x1f8a126c…9aa5
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x482471ad…122f
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 0x5e1c23e9cd…6d4f81
Audit this contract →
← previous block·next block →recent activity