← previous blocknext block →recent activity

Analyzing

Block #74,010,390

10 transactions · 7 stateful · 2026-05-12 02:07:14 UTC

Parallelism

70/100

Blocked

29%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,010,390  ·  10 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x1f1df0cc…bea6

0x065c9d…c394

2 touches
0 conflicts

0x5a003a00…a0f0

0x065c9d…c394

2 touches
0 conflicts

0x61ccbb10…4a5c

0x065c9d…c394

2 touches
0 conflicts

0xe515b77a…ba60

0x065c9d…c394

2 touches
0 conflicts

0xe5defdb6…4dd1

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: 0x065c9d28…a9c394

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity