← previous blocknext block →recent activity
Analyzing
Block #95,202,690
24 transactions · 23 stateful · 2026-08-12 00:19:20 UTC
Parallelism
75/100
Blocked
52%
Avg conflicts / tx
1.04
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,202,690 · 24 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
1w02w13w25w06w19w110w212w013w114w215w316w417w519w321w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf79df061…e005
0xe52b14…7230
12 touches
15 conflicts
0x8ffa3328…ce11
0xe52b14…7230
10 touches
10 conflicts
0xe1902c61…65ad
0xe52b14…7230
10 touches
10 conflicts
0xa6e37efb…afc2
0xe52b14…7230
10 touches
10 conflicts
0xa6e37efb…afc0
0xe52b14…7230
10 touches
10 conflicts
0xab14878b…91d5
0xe52b14…7230
8 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xc824469a…6425
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: 0xe52b1424…bb7230
15 conflicts on slot 0xf79df061c7…91e005
Audit this contract →
← previous block·next block →recent activity