← previous blocknext block →recent activity

Analyzing

Block #93,857,249

14 transactions · 13 stateful · 2026-08-07 07:13:32 UTC

Parallelism

86/100

Blocked

23%

Avg conflicts / tx

0.29

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #93,857,249  ·  14 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xd4702f73…926c

0x34b655…2a6f

4 touches
1 conflict

0x709c2293…6c55

0x34b655…2a6f

4 touches
1 conflict

0x709c2293…6c56

0x34b655…2a6f

4 touches
1 conflict

0x853675a4…4ab4

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x0d256437…ceb8

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

1 conflict on slot 0xd4702f73d1…46926c

← previous block·next block →recent activity