← previous blocknext block →recent activity

Analyzing

Block #74,896,317

33 transactions · 22 stateful · 2026-05-16 04:34:47 UTC

Parallelism

85/100

Blocked

55%

Avg conflicts / tx

0.7

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,896,317  ·  33 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

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0xfc3aa93a…52e3

0xd32edf…ff58

7 touches
6 conflicts

0x8a35acfb…d1a8

0x8d66a4…3095

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xfe2bac2b…2cec

0x065c9d…c394

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0x8a35acfb…d1a7

0x8d66a4…3095

6 touches
3 conflicts

0x8a35acfb…d1a9

0x8d66a4…3095

5 touches
3 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: 0x754704bc…afb603

6 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity