← previous blocknext block →recent activity

Analyzing

Block #90,810,194

19 transactions · 18 stateful · 2026-07-27 15:42:07 UTC

Parallelism

58/100

Blocked

61%

Avg conflicts / tx

1.58

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #90,810,194  ·  19 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x53f393fa…00b9

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xe718c0a6…7693

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x58d6b9cf…7c9e

0x34b655…2a6f

4 touches
1 conflict

0x6bdb9869…7558

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

15 conflicts on slot 0x53f393fafd…2a00b9

← previous block·next block →recent activity