← previous blocknext block →recent activity

Analyzing

Block #91,070,102

21 transactions · 17 stateful · 2026-07-28 13:30:32 UTC

Parallelism

67/100

Blocked

53%

Avg conflicts / tx

0.9

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #91,070,102  ·  21 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

0x6fe7d366…78ff

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…0002

0x48cba2…b48b

6 touches
3 conflicts

0x23e706b3…0e16

0x34b655…2a6f

4 touches
1 conflict

0x312193ac…70a7

0x34b655…2a6f

4 touches
1 conflict

0x37d710c8…45c1

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x540028d7…83af

0x34b655…2a6f

4 touches
1 conflict

0x818e1296…f4d7

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

10 conflicts on slot 0x6fe7d366be…a578ff

← previous block·next block →recent activity