← previous blocknext block →recent activity

Analyzing

Block #91,211,813

21 transactions · 19 stateful · 2026-07-29 01:23:29 UTC

Parallelism

86/100

Blocked

37%

Avg conflicts / tx

0.48

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #91,211,813  ·  21 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xefcdf197…96a2

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x0733be30…112f

0x34b655…2a6f

6 touches
3 conflicts

0x4e782273…1690

0x34b655…2a6f

4 touches
1 conflict

0x6ef08b1e…eab6

0x34b655…2a6f

4 touches
1 conflict

0x85eb1316…bb9e

0x34b655…2a6f

4 touches
1 conflict

0x98459f89…575d

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

3 conflicts on slot 0xefcdf19725…1096a2

← previous block·next block →recent activity