← previous blocknext block →recent activity
Analyzing
Block #99,308,493
24 transactions · 23 stateful · 2026-08-26 10:45:28 UTC
Parallelism
67/100
Blocked
52%
Avg conflicts / tx
0.92
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #99,308,493 · 24 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
1w02w16w07w08w09w110w212w313w414w515w118w120w421w522w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa5b4eb1b…616b
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x4e58deff…c5d0
0x34b655…2a6f
6 touches
3 conflicts
0x38bcfe5f…6c71
0x34b655…2a6f
6 touches
3 conflicts
0x62910921…3016
0x34b655…2a6f
6 touches
3 conflicts
0x932a9590…0b19
0x34b655…2a6f
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
6 conflicts on slot 0xa5b4eb1ba4…5d616b
Audit this contract →
← previous block·next block →recent activity