← previous blocknext block →recent activity
Analyzing
Block #99,934,373
25 transactions · 25 stateful · 2026-08-28 15:29:45 UTC
Parallelism
76/100
Blocked
40%
Avg conflicts / tx
0.96
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,934,373 · 25 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
1w02w04w16w08w09w110w211w313w014w115w118w419w123w224w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xef3f5637…f47c
0x34b655…2a6f
8 touches
6 conflicts
0x898a1a2f…bf47
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xf15273a1…2c52
0x34b655…2a6f
6 touches
3 conflicts
0x6fce7a05…d778
0x34b655…2a6f
6 touches
3 conflicts
0xa9af9157…5a6e
0x34b655…2a6f
6 touches
3 conflicts
0xa66499c2…9f47
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 0xef3f5637ee…e7f47c
Audit this contract →
← previous block·next block →recent activity