← previous blocknext block →recent activity

Analyzing

Block #91,417,839

20 transactions · 16 stateful · 2026-07-29 18:41:23 UTC

Parallelism

70/100

Blocked

50%

Avg conflicts / tx

0.6

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #91,417,839  ·  20 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x41e2551c…5586

0x34b655…2a6f

4 touches
1 conflict

0x5502e1cc…3910

0x34b655…2a6f

4 touches
1 conflict

0x7e7de6d7…48be

0x34b655…2a6f

4 touches
1 conflict

0xb9834665…e363

0x34b655…2a6f

4 touches
1 conflict

0xc0eb79d1…29a4

0x34b655…2a6f

4 touches
1 conflict

0xdbd503eb…2b83

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

6 conflicts on slot 0x6fe7d366be…a578ff

← previous block·next block →recent activity