← previous blocknext block →recent activity

Analyzing

Block #90,796,171

24 transactions · 21 stateful · 2026-07-27 14:31:31 UTC

Parallelism

50/100

Blocked

62%

Avg conflicts / tx

1.75

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #90,796,171  ·  24 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

12 touches
15 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

12 touches
15 conflicts

0x4cabb80a…46bf

0x34b655…2a6f

6 touches
3 conflicts

0x310afe2c…83e1

0x34b655…2a6f

6 touches
3 conflicts

0x16dcea2f…25e6

0x34b655…2a6f

6 touches
3 conflicts

0x2c2db8e9…fdc7

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity