← previous blocknext block →recent activity

Analyzing

Block #91,966,868

20 transactions · 19 stateful · 2026-07-31 16:44:17 UTC

Parallelism

70/100

Blocked

42%

Avg conflicts / tx

0.8

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #91,966,868  ·  20 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x02991b41…19e6

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x6f7837a5…7daf

0x34b655…2a6f

8 touches
6 conflicts

0x093cd412…f6f8

0x7b9256…1fb2

6 touches
3 conflicts

0x29fa1840…77ab

0x7b9256…1fb2

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

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

10 conflicts on slot 0x02991b41c5…1a19e6

← previous block·next block →recent activity