← previous blocknext block →recent activity

Analyzing

Block #74,736,265

36 transactions · 27 stateful · 2026-05-15 10:46:19 UTC

Parallelism

78/100

Blocked

63%

Avg conflicts / tx

1.17

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,736,265  ·  36 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

0xd4ea065a…ba11

0xd32edf…ff58

13 touches
21 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0xcb45d9d6…cb81

0x1b6862…e19c

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x6af306bb…2e81

0x3bd359…433a

6 touches
3 conflicts

0xf3d7a307…4d63

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0019

0x1b6862…e19c

6 touches
3 conflicts

0x08943ea2…ed03

0x754704…b603

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

21 conflicts on slot 0xd4ea065a1d…daba11

← previous block·next block →recent activity