← previous blocknext block →recent activity

Analyzing

Block #90,530,937

21 transactions · 18 stateful · 2026-07-26 16:17:12 UTC

Parallelism

67/100

Blocked

50%

Avg conflicts / tx

0.9

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #90,530,937  ·  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

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x1bf8d2af…d140

0x34b655…2a6f

6 touches
3 conflicts

0x1fa1e1c3…2998

0xd32edf…ff58

5 touches
3 conflicts

0x48b13e5e…3c2a

0x34b655…2a6f

4 touches
1 conflict

0x493b2422…4a08

0x34b655…2a6f

4 touches
1 conflict

0x83395486…931b

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 0xc824469a90…af6425

← previous block·next block →recent activity