← previous blocknext block →recent activity

Analyzing

Block #91,244,099

20 transactions · 19 stateful · 2026-07-29 04:05:54 UTC

Parallelism

65/100

Blocked

42%

Avg conflicts / tx

0.8

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #91,244,099  ·  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

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x966e45cf…0f25

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x4f3a6b4a…3819

0x34b655…2a6f

4 touches
1 conflict

0x5229d4af…173b

0x34b655…2a6f

4 touches
1 conflict

0x7c93b38a…9e69

0x34b655…2a6f

4 touches
1 conflict

0x86b6d4a1…728c

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

10 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity