← previous blocknext block →recent activity

Analyzing

Block #74,287,342

11 transactions · 10 stateful · 2026-05-13 08:49:02 UTC

Parallelism

64/100

Blocked

30%

Avg conflicts / tx

0.64

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,287,342  ·  11 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x335a161d…fe7f

0x000000…012a

6 touches
3 conflicts

0x155a3a69…116e

0x699abc…6a3b

6 touches
3 conflicts

0x29dcc18f…0a5f

0x699abc…6a3b

6 touches
3 conflicts

0x0d0b2509…074d

0x3bd359…433a

4 touches
1 conflict

0xe6455d1f…1029

0x754704…b603

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0015

0x1b6862…e19c

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

6 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity