← previous blocknext block →recent activity

Analyzing

Block #90,992,070

20 transactions · 18 stateful · 2026-07-28 06:57:13 UTC

Parallelism

65/100

Blocked

44%

Avg conflicts / tx

1.15

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #90,992,070  ·  20 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

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0x6e0e8837…2e59

0x34b655…2a6f

6 touches
3 conflicts

0x421099c9…8896

0x34b655…2a6f

6 touches
3 conflicts

0x3e4af36e…07ae

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x48965dfe…432b

0x34b655…2a6f

4 touches
1 conflict

0x508bbf1b…fe95

0x34b655…2a6f

4 touches
1 conflict

0x7182a94f…dc78

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

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity