← previous blocknext block →recent activity
Analyzing
Block #99,503,967
22 transactions · 22 stateful · 2026-08-27 03:09:42 UTC
Parallelism
86/100
Blocked
14%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,503,967 · 22 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w110w011w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x84a76404…18f8
0x8964d7…10f8
6 touches
3 conflicts
0x84a76404…18fa
0x8964d7…10f8
6 touches
3 conflicts
0xb4a48d23…e29f
0x8964d7…10f8
6 touches
3 conflicts
0xb4a48d23…e2a0
0x8964d7…10f8
6 touches
3 conflicts
0xb4a48d23…e2a2
0x8964d7…10f8
6 touches
3 conflicts
0x84a76404…18f9
0x8964d7…10f8
6 touches
3 conflicts
0x177211e2…1c2d
0x754704…b603
6 touches
3 conflicts
0x2a07e64e…fe77
0x754704…b603
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: 0x8964d7c9…5b10f8
3 conflicts on slot 0x84a76404b4…9e18f8
Audit this contract →
← previous block·next block →recent activity