← previous blocknext block →recent activity

Analyzing

Block #91,404,599

16 transactions · 16 stateful · 2026-07-29 17:34:31 UTC

Parallelism

56/100

Blocked

38%

Avg conflicts / tx

0.69

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #91,404,599  ·  16 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x03aa8b26…118a

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0xefcdf197…96a2

0x34b655…2a6f

6 touches
3 conflicts

0xdaf240c7…95b0

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0x2840c278…bbc7

0x34b655…2a6f

4 touches
1 conflict

0x0899947a…48a7

0x34b655…2a6f

4 touches
1 conflict

0x34a1ee7e…fb20

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 0x03aa8b260f…60118a

← previous block·next block →recent activity