← previous blocknext block →recent activity

Analyzing

Block #90,786,365

19 transactions · 17 stateful · 2026-07-27 13:42:09 UTC

Parallelism

68/100

Blocked

47%

Avg conflicts / tx

0.84

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #90,786,365  ·  19 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xe2fe788f…a454

0x34b655…2a6f

6 touches
3 conflicts

0x64aaadbf…f9f3

0x34b655…2a6f

6 touches
3 conflicts

0x680ca7d7…2df4

0x34b655…2a6f

4 touches
1 conflict

0x699ee60f…de01

0x34b655…2a6f

4 touches
1 conflict

0x7464c5f1…9461

0x34b655…2a6f

4 touches
1 conflict

0x78346476…4311

0x34b655…2a6f

4 touches
1 conflict

0x82d510df…8d5c

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity