← previous blocknext block →recent activity

Analyzing

Block #91,957,472

19 transactions · 17 stateful · 2026-07-31 15:57:02 UTC

Parallelism

79/100

Blocked

41%

Avg conflicts / tx

0.42

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #91,957,472  ·  19 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x11b69a7e…334e

0x01bff4…1071

4 touches
1 conflict

0x493e876e…c60c

0x01bff4…1071

4 touches
1 conflict

0x6927695a…d15b

0x01bff4…1071

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x5540f956…69e8

0x065c9d…c394

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0xf7640726…19a2

0x2a68ba…90c5

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 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity