← previous blocknext block →recent activity

Analyzing

Block #74,355,826

28 transactions · 22 stateful · 2026-05-13 16:24:36 UTC

Parallelism

79/100

Blocked

73%

Avg conflicts / tx

1.39

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,355,826  ·  28 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x8c49c85c…ee96

0x34b655…2a6f

12 touches
15 conflicts

0xfa126cd2…2f25

0xd32edf…ff58

11 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xea02471d…1542

0x34b655…2a6f

10 touches
10 conflicts

0xbb12db23…857e

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…002a

0x1b6862…e19c

6 touches
3 conflicts

0x083a8763…5a7a

0x1b6862…e19c

6 touches
3 conflicts

0xf3d10975…0d07

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 0x8c49c85c3e…afee96

← previous block·next block →recent activity