← previous blocknext block →recent activity

Analyzing

Block #90,883,694

20 transactions · 17 stateful · 2026-07-27 21:51:56 UTC

Parallelism

90/100

Blocked

29%

Avg conflicts / tx

0.25

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #90,883,694  ·  20 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x00966e54…7d1d

0x34b655…2a6f

4 touches
1 conflict

0x199ba9d0…0bba

0x34b655…2a6f

4 touches
1 conflict

0x25329a48…4e00

0x34b655…2a6f

4 touches
1 conflict

0x2f4b1dc8…e9fa

0x34b655…2a6f

4 touches
1 conflict

0x3beed133…720d

0x34b655…2a6f

4 touches
1 conflict

0x41e2ea73…ddf8

0x34b655…2a6f

4 touches
1 conflict

0x49244eb9…1553

0x34b655…2a6f

4 touches
1 conflict

0x56b82b8c…e6d5

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

1 conflict on slot 0x00966e5492…9a7d1d

← previous block·next block →recent activity