← previous blocknext block →recent activity

Analyzing

Block #90,796,562

30 transactions · 19 stateful · 2026-07-27 14:33:29 UTC

Parallelism

77/100

Blocked

42%

Avg conflicts / tx

0.57

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #90,796,562  ·  30 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x4cabb80a…46bf

0x34b655…2a6f

8 touches
6 conflicts

0xa3f6f7c8…2436

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x1a5d321d…a474

0x34b655…2a6f

6 touches
3 conflicts

0x45ef9175…5ab2

0x34b655…2a6f

6 touches
3 conflicts

0x5cc49f5b…c6db

0x34b655…2a6f

4 touches
1 conflict

0x6fe7d366…78ff

0x34b655…2a6f

4 touches
1 conflict

0xcf4ef432…d64c

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 0x4cabb80a0e…7546bf

← previous block·next block →recent activity