← previous blocknext block →recent activity

Analyzing

Block #74,351,340

47 transactions · 28 stateful · 2026-05-13 15:54:44 UTC

Parallelism

74/100

Blocked

64%

Avg conflicts / tx

1.62

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #74,351,340  ·  47 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

0x946968f2…8a59

0xd32edf…ff58

23 touches
66 conflicts

0x41755291…977f

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0x00000000…0019

0x1b6862…e19c

4 touches
1 conflict

0xcb45d9d6…cb81

0x1b6862…e19c

4 touches
1 conflict

0x4d3e58e0…a2d7

0x34b655…2a6f

4 touches
1 conflict

0x8c49c85c…ee96

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

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

66 conflicts on slot 0x946968f243…1d8a59

← previous block·next block →recent activity