← previous blocknext block →recent activity

Analyzing

Block #90,894,073

20 transactions · 18 stateful · 2026-07-27 22:44:09 UTC

Parallelism

60/100

Blocked

56%

Avg conflicts / tx

1.3

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #90,894,073  ·  20 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

0x8252706a…7ca5

0x34b655…2a6f

8 touches
6 conflicts

0x96dd83e6…a507

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0x2dfde2ed…8801

0x34b655…2a6f

4 touches
1 conflict

0x2fade833…5de4

0x34b655…2a6f

4 touches
1 conflict

0x4c5b064f…1498

0x34b655…2a6f

4 touches
1 conflict

0x6f6fc26c…3e34

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

6 conflicts on slot 0x8252706a8a…797ca5

← previous block·next block →recent activity