← previous blocknext block →recent activity

Analyzing

Block #91,435,525

22 transactions · 21 stateful · 2026-07-29 20:11:15 UTC

Parallelism

59/100

Blocked

57%

Avg conflicts / tx

1.45

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #91,435,525  ·  22 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xda2ee2e7…968a

0x34b655…2a6f

8 touches
6 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0x424934c8…f2f1

0x34b655…2a6f

8 touches
6 conflicts

0x08a39015…efa0

0x34b655…2a6f

6 touches
3 conflicts

0x442e26a3…e968

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xb000406f…07ed

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

6 conflicts on slot 0xda2ee2e777…e7968a

← previous block·next block →recent activity