← previous blocknext block →recent activity

Analyzing

Block #73,920,928

16 transactions · 15 stateful · 2026-05-11 16:09:08 UTC

Parallelism

63/100

Blocked

53%

Avg conflicts / tx

1.19

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,920,928  ·  16 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

0x052ae9c7…a3b0

0xd32edf…ff58

11 touches
15 conflicts

0x03df3a18…58e7

0x34b655…2a6f

6 touches
3 conflicts

0xee230b20…5a0f

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0019

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0029

0x1b6862…e19c

4 touches
1 conflict

0x1319ae2c…7f9a

0x34b655…2a6f

4 touches
1 conflict

0x4f483049…3cc7

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

15 conflicts on slot 0x052ae9c791…84a3b0

← previous block·next block →recent activity