← previous blocknext block →recent activity
Analyzing
Block #99,479,885
14 transactions · 14 stateful · 2026-08-27 01:08:27 UTC
Parallelism
50/100
Blocked
43%
Avg conflicts / tx
0.93
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,479,885 · 14 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
3w06w17w210w311w412w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd814f518…f5b4
0x34b655…2a6f
6 touches
3 conflicts
0xe098738f…9bbe
0x34b655…2a6f
4 touches
1 conflict
0x1917fdfd…f3af
0x34b655…2a6f
4 touches
1 conflict
0x250972e8…5f84
0x34b655…2a6f
4 touches
1 conflict
0x574628e9…dcc3
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity