← previous blocknext block →recent activity

Analyzing

Block #90,826,633

16 transactions · 16 stateful · 2026-07-27 17:04:52 UTC

Parallelism

56/100

Blocked

63%

Avg conflicts / tx

1.44

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #90,826,633  ·  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

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0x482471ad…122f

0x34b655…2a6f

12 touches
15 conflicts

0x2f4beec6…ab79

0x34b655…2a6f

8 touches
6 conflicts

0x69a45f39…39aa

0x34b655…2a6f

8 touches
6 conflicts

0xfe2577ac…677b

0x34b655…2a6f

6 touches
3 conflicts

0xd192f4ed…d7ec

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…00c9

0x34b655…2a6f

6 touches
3 conflicts

0xf77a2986…931c

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

15 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity