← previous blocknext block →recent activity

Analyzing

Block #90,680,590

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

Parallelism

65/100

Blocked

50%

Avg conflicts / tx

1.18

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #90,680,590  ·  17 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

12 touches
15 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x320701d5…f9f3

0x34b655…2a6f

4 touches
1 conflict

0x455c94ee…3b8b

0x34b655…2a6f

4 touches
1 conflict

0x5655f5c3…6b75

0x34b655…2a6f

4 touches
1 conflict

0x70cfbacf…5c46

0x34b655…2a6f

4 touches
1 conflict

0x7103aaf4…ddc5

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

← previous block·next block →recent activity