← previous blocknext block →recent activity

Analyzing

Block #90,817,537

21 transactions · 19 stateful · 2026-07-27 16:19:06 UTC

Parallelism

81/100

Blocked

32%

Avg conflicts / tx

0.33

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #90,817,537  ·  21 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…004c

0x80c745…7210

4 touches
1 conflict

0x1d6ce97a…901b

0x34b655…2a6f

4 touches
1 conflict

0x22ce1aa0…6e58

0x34b655…2a6f

4 touches
1 conflict

0x30a40b5a…8d15

0x34b655…2a6f

4 touches
1 conflict

0x41377979…0a18

0x34b655…2a6f

4 touches
1 conflict

0x5f56ffe5…09c0

0x34b655…2a6f

4 touches
1 conflict

0x94bb14fe…8f47

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

← previous block·next block →recent activity