← previous blocknext block →recent activity

Analyzing

Block #74,314,305

16 transactions · 11 stateful · 2026-05-13 11:48:32 UTC

Parallelism

69/100

Blocked

36%

Avg conflicts / tx

0.63

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,314,305  ·  16 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xf448fe6a…dfd8

0xd32edf…ff58

9 touches
10 conflicts

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x335a161d…fe7f

0x000000…012a

2 touches
0 conflicts

0x78ae17f2…53be

0x000000…012a

2 touches
0 conflicts

0x00000000…0001

0x010592…1c83

2 touches
0 conflicts

0x00000000…0006

0x010592…1c83

2 touches
0 conflicts

0x37d24f4a…7d1a

0x010592…1c83

2 touches
0 conflicts

0x94f01f1b…6c96

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

10 conflicts on slot 0xf448fe6a65…9adfd8

← previous block·next block →recent activity