← previous blocknext block →recent activity

Analyzing

Block #90,643,733

17 transactions · 17 stateful · 2026-07-27 01:44:38 UTC

Parallelism

76/100

Blocked

29%

Avg conflicts / tx

0.41

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #90,643,733  ·  17 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

0xe66201d4…84f1

0x34b655…2a6f

6 touches
3 conflicts

0xa6b89ebb…a66e

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xbf7d13d4…ff69

0x34b655…2a6f

4 touches
1 conflict

0x10379e8d…3675

0x34b655…2a6f

4 touches
1 conflict

0x201d7cf1…f7f2

0x34b655…2a6f

4 touches
1 conflict

0x4d58476d…3e80

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 0xe66201d40c…1e84f1

← previous block·next block →recent activity