← previous blocknext block →recent activity

Analyzing

Block #74,336,166

43 transactions · 34 stateful · 2026-05-13 14:13:53 UTC

Parallelism

81/100

Blocked

62%

Avg conflicts / tx

1.4

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,336,166  ·  43 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x5bded9d7…5e1a

0xd32edf…ff58

15 touches
28 conflicts

0x00000000…0002

0xab3526…fa38

12 touches
15 conflicts

0xf3981be5…2c47

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…0019

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0029

0x1b6862…e19c

8 touches
6 conflicts

0xd18a8dca…452a

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 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: 0xd32edf66…9fff58

28 conflicts on slot 0x5bded9d7c3…295e1a

← previous block·next block →recent activity