← previous blocknext block →recent activity

Analyzing

Block #74,452,852

30 transactions · 14 stateful · 2026-05-14 03:10:27 UTC

Parallelism

80/100

Blocked

43%

Avg conflicts / tx

0.53

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,452,852  ·  30 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

0x80782aff…7e73

0xd32edf…ff58

11 touches
15 conflicts

0x74045a23…62b9

0x065c9d…c394

3 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x644ba748…ce1a

0x0555e3…2b9c

2 touches
0 conflicts

0x846f2172…fd54

0x0555e3…2b9c

2 touches
0 conflicts

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x0d57da06…62cb

0x065c9d…c394

2 touches
0 conflicts

0x3cd91bc3…061f

0x065c9d…c394

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 0x80782aff9c…ce7e73

← previous block·next block →recent activity