← previous blocknext block →recent activity

Analyzing

Block #91,097,235

25 transactions · 23 stateful · 2026-07-28 15:47:07 UTC

Parallelism

56/100

Blocked

52%

Avg conflicts / tx

2.16

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #91,097,235  ·  25 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x482471ad…122f

0x34b655…2a6f

20 touches
45 conflicts

0xc824469a…6425

0x34b655…2a6f

18 touches
36 conflicts

0xbde524f4…43bf

0x34b655…2a6f

14 touches
21 conflicts

0x705ab4ae…0162

0x34b655…2a6f

12 touches
15 conflicts

0xadb81d16…8380

0x34b655…2a6f

10 touches
10 conflicts

0xda203c6e…d450

0x34b655…2a6f

5 touches
3 conflicts

0x06e3a739…7d61

0x34b655…2a6f

5 touches
3 conflicts

0xa779293b…5e59

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

45 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity