← previous blocknext block →recent activity

Analyzing

Block #91,406,374

19 transactions · 16 stateful · 2026-07-29 17:43:30 UTC

Parallelism

79/100

Blocked

25%

Avg conflicts / tx

0.21

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #91,406,374  ·  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

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xefcdf197…96a2

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x07d8b1e8…78c6

0x34b655…2a6f

4 touches
1 conflict

0x152f8e3d…3da0

0x34b655…2a6f

4 touches
1 conflict

0x1d6ce97a…901b

0x34b655…2a6f

4 touches
1 conflict

0x36a76bd2…1fb0

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

1 conflict on slot 0x482471adbb…39122f

← previous block·next block →recent activity