← previous blocknext block →recent activity

Analyzing

Block #91,982,184

27 transactions · 23 stateful · 2026-07-31 18:01:19 UTC

Parallelism

56/100

Blocked

61%

Avg conflicts / tx

2.26

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #91,982,184  ·  27 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

0x6f900be0…cd6e

0x34b655…2a6f

18 touches
36 conflicts

0xc824469a…6425

0x34b655…2a6f

16 touches
28 conflicts

0x482471ad…122f

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x86109e30…26c2

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6426

0x34b655…2a6f

8 touches
6 conflicts

0xbbeac3b7…c14b

0x34b655…2a6f

8 touches
6 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 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

36 conflicts on slot 0x6f900be04d…4ccd6e

← previous block·next block →recent activity