← previous blocknext block →recent activity

Analyzing

Block #74,352,009

32 transactions · 26 stateful · 2026-05-13 15:59:11 UTC

Parallelism

78/100

Blocked

58%

Avg conflicts / tx

1.16

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,352,009  ·  32 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x8c49c85c…ee96

0x34b655…2a6f

12 touches
15 conflicts

0x0425e443…b0e7

0xd32edf…ff58

9 touches
10 conflicts

0xcb45d9d6…cb81

0x1b6862…e19c

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0019

0x1b6862…e19c

8 touches
6 conflicts

0x56a919c4…ab49

0xee8c0e…1242

6 touches
3 conflicts

0x070a562a…8147

0x34b655…2a6f

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: 0x34b6552d…112a6f

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity