← previous blocknext block →recent activity

Analyzing

Block #90,793,368

21 transactions · 19 stateful · 2026-07-27 14:17:25 UTC

Parallelism

71/100

Blocked

42%

Avg conflicts / tx

0.67

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #90,793,368  ·  21 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

0x007892de…5752

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xb2022d4d…0ca0

0xa6afd3…d132

4 touches
1 conflict

0x80398c66…f3cc

0x34b655…2a6f

4 touches
1 conflict

0x917f99a5…7989

0x34b655…2a6f

4 touches
1 conflict

0x9a4b9740…61cf

0x34b655…2a6f

4 touches
1 conflict

0xaa9f27b0…9cf2

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 0x007892de1e…635752

← previous block·next block →recent activity