← previous blocknext block →recent activity

Analyzing

Block #74,645,995

35 transactions · 25 stateful · 2026-05-15 00:43:56 UTC

Parallelism

77/100

Blocked

64%

Avg conflicts / tx

1.4

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,645,995  ·  35 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

0x919316f3…d019

0xd32edf…ff58

15 touches
28 conflicts

0xcb45d9d6…cb87

0x1b6862…e19c

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xf3981be5…2c47

0x34b655…2a6f

8 touches
6 conflicts

0xffe431af…8faa

0x065c9d…c394

8 touches
6 conflicts

0x00000000…001f

0x1b6862…e19c

8 touches
6 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

6 touches
3 conflicts

0x641245e3…6323

0xc8689a…ee79

6 touches
3 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 0x919316f3c8…2dd019

← previous block·next block →recent activity