← previous blocknext block →recent activity

Analyzing

Block #91,417,173

18 transactions · 16 stateful · 2026-07-29 18:38:02 UTC

Parallelism

83/100

Blocked

44%

Avg conflicts / tx

0.56

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #91,417,173  ·  18 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0x00000000…0002

0x48cba2…b48b

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x1e8c788e…69d9

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x30ae635d…5e67

0x34b655…2a6f

4 touches
1 conflict

0x326a02b5…8dad

0x34b655…2a6f

4 touches
1 conflict

0x5cc0e9c8…3ae6

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

3 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity