← previous blocknext block →recent activity

Analyzing

Block #74,284,079

11 transactions · 8 stateful · 2026-05-13 08:27:22 UTC

Parallelism

82/100

Blocked

13%

Avg conflicts / tx

0.09

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,284,079  ·  11 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

4 touches
1 conflict

0x335a161d…fe7f

0x000000…012a

4 touches
1 conflict

0x18f9ec19…56db

0x699abc…6a3b

4 touches
1 conflict

0xbca294ab…641e

0x699abc…6a3b

3 touches
1 conflict

0x194f2c02…19e6

0x2a68ba…90c5

2 touches
0 conflicts

0x0fff4a9f…b7f6

0x34b655…2a6f

2 touches
0 conflicts

0x1efe2d7f…d75f

0x34b655…2a6f

2 touches
0 conflicts

0x26ecf235…37ba

0x34b655…2a6f

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

1 conflict on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity