← previous blocknext block →recent activity

Analyzing

Block #90,817,032

30 transactions · 29 stateful · 2026-07-27 16:16:33 UTC

Parallelism

60/100

Blocked

59%

Avg conflicts / tx

1.93

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #90,817,032  ·  30 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

18 touches
36 conflicts

0x4c188934…158e

0x34b655…2a6f

8 touches
6 conflicts

0x96dd83e6…a507

0x34b655…2a6f

8 touches
6 conflicts

0x02679875…8d2f

0x34b655…2a6f

6 touches
3 conflicts

0x2f4b1dc8…e9fa

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

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

36 conflicts on slot 0x6fe7d366be…a578ff

← previous block·next block →recent activity