← previous blocknext block →recent activity

Analyzing

Block #91,210,645

21 transactions · 21 stateful · 2026-07-29 01:17:37 UTC

Parallelism

76/100

Blocked

33%

Avg conflicts / tx

1.1

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #91,210,645  ·  21 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xbbeac3b7…c14b

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x6ba89834…1826

0x34b655…2a6f

6 touches
3 conflicts

0xd4b83c55…2e87

0x34b655…2a6f

6 touches
3 conflicts

0x76ed8777…1e5f

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 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

10 conflicts on slot 0xbbeac3b703…d0c14b

← previous block·next block →recent activity