← previous blocknext block →recent activity
Analyzing
Block #99,318,896
30 transactions · 25 stateful · 2026-08-26 11:37:47 UTC
Parallelism
53/100
Blocked
68%
Avg conflicts / tx
2.4
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #99,318,896 · 30 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w09w110w211w212w314w415w516w617w118w722w724w826w1027w1128w1229w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x79347b24…9fba
0x34b655…2a6f
8 touches
6 conflicts
0xb409e204…89ac
0x34b655…2a6f
8 touches
6 conflicts
0x81716ce9…095f
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
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
36 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity