← previous blocknext block →recent activity

Analyzing

Block #90,821,025

19 transactions · 18 stateful · 2026-07-27 16:36:39 UTC

Parallelism

79/100

Blocked

44%

Avg conflicts / tx

0.68

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #90,821,025  ·  19 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x26d1c221…4d2a

0x34b655…2a6f

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x0d488000…3831

0x34b655…2a6f

4 touches
1 conflict

0x24eaf46d…8c2e

0x34b655…2a6f

4 touches
1 conflict

0x25191452…d2ed

0x34b655…2a6f

4 touches
1 conflict

0x2f4b1dc8…e9fa

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x5af098c7…4806

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

3 conflicts on slot 0x26d1c221d7…ef4d2a

← previous block·next block →recent activity