← previous blocknext block →recent activity

Analyzing

Block #74,436,481

32 transactions · 24 stateful · 2026-05-14 01:21:32 UTC

Parallelism

72/100

Blocked

54%

Avg conflicts / tx

1.19

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,436,481  ·  32 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x47ef9ee5…d9c8

0xd32edf…ff58

15 touches
28 conflicts

0xcb45d9d6…cb83

0x1b6862…e19c

6 touches
3 conflicts

0x4dd1db39…a997

0x188d58…ea8e

6 touches
3 conflicts

0x4dd1db39…a994

0x188d58…ea8e

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x00000000…001b

0x1b6862…e19c

6 touches
3 conflicts

0x64e2698f…7e89

0x188d58…ea8e

4 touches
1 conflict

0x64e2698f…7e8a

0x188d58…ea8e

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

28 conflicts on slot 0x47ef9ee5c8…cbd9c8

← previous block·next block →recent activity