← previous blocknext block →recent activity

Analyzing

Block #73,987,806

16 transactions · 11 stateful · 2026-05-11 23:35:11 UTC

Parallelism

81/100

Blocked

36%

Avg conflicts / tx

0.31

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,987,806  ·  16 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xa2fe28db…7db5

0xd32edf…ff58

5 touches
3 conflicts

0x5138188e…796b

0x34b655…2a6f

4 touches
1 conflict

0x192cb36c…648d

0x34b655…2a6f

4 touches
1 conflict

0x3c6cf955…1112

0x34b655…2a6f

4 touches
1 conflict

0x97b0b2ee…4666

0x34b655…2a6f

4 touches
1 conflict

0xa15427f6…d932

0x34b655…2a6f

4 touches
1 conflict

0xa92c8763…6d7f

0x34b655…2a6f

4 touches
1 conflict

0xc08384da…ecb7

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

3 conflicts on slot 0xa2fe28db51…767db5

← previous block·next block →recent activity