← previous blocknext block →recent activity

Analyzing

Block #74,382,918

21 transactions · 15 stateful · 2026-05-13 19:24:56 UTC

Parallelism

71/100

Blocked

40%

Avg conflicts / tx

0.76

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,382,918  ·  21 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

0x8feac12e…f910

0xd32edf…ff58

11 touches
15 conflicts

0xa02838a3…bc54

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0x78ae17f2…53be

0x000000…012a

2 touches
0 conflicts

0x00000000…0001

0x010592…1c83

2 touches
0 conflicts

0x00000000…0006

0x010592…1c83

2 touches
0 conflicts

0x26a59410…530c

0x010592…1c83

2 touches
0 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

15 conflicts on slot 0x8feac12e0b…35f910

← previous block·next block →recent activity