← previous blocknext block →recent activity

Analyzing

Block #74,917,986

25 transactions · 10 stateful · 2026-05-16 06:59:18 UTC

Parallelism

80/100

Blocked

40%

Avg conflicts / tx

0.4

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,917,986  ·  25 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

0x217bbfe4…5001

0xd32edf…ff58

9 touches
10 conflicts

0x394c3833…b4ac

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001d

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002d

0x1b6862…e19c

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

10 conflicts on slot 0x217bbfe4c0…285001

← previous block·next block →recent activity