← previous blocknext block →recent activity

Analyzing

Block #91,248,623

22 transactions · 21 stateful · 2026-07-29 04:28:43 UTC

Parallelism

64/100

Blocked

52%

Avg conflicts / tx

1.32

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #91,248,623  ·  22 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

12 touches
15 conflicts

0x1526b11f…8b21

0x34b655…2a6f

10 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0xf41875fa…57f1

0x34b655…2a6f

10 touches
10 conflicts

0x3f5831e5…02b2

0x34b655…2a6f

6 touches
3 conflicts

0x81561f70…fefd

0x34b655…2a6f

6 touches
3 conflicts

0x88e771e8…7d4a

0x34b655…2a6f

6 touches
3 conflicts

0x6e6b8ec7…2197

0x34b655…2a6f

6 touches
3 conflicts

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 0xc824469a90…af6425

← previous block·next block →recent activity