← previous blocknext block →recent activity

Analyzing

Block #91,409,683

37 transactions · 27 stateful · 2026-07-29 18:00:18 UTC

Parallelism

76/100

Blocked

59%

Avg conflicts / tx

1.24

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #91,409,683  ·  37 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

0x00000000…0002

0x48cba2…b48b

18 touches
36 conflicts

0x878555be…903e

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x50260e8c…4789

0x34b655…2a6f

4 touches
1 conflict

0x5475cd67…5763

0x34b655…2a6f

4 touches
1 conflict

0x7aad02c6…b979

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: 0x48cba278…e2b48b

36 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity