← previous blocknext block →recent activity

Analyzing

Block #74,916,232

13 transactions · 9 stateful · 2026-05-16 06:47:35 UTC

Parallelism

85/100

Blocked

11%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,916,232  ·  13 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

0xf93e2aa1…f3b7

0x065c9d…c394

4 touches
1 conflict

0x422a4b4c…61c6

0x065c9d…c394

3 touches
1 conflict

0xaa06f8d0…f6fc

0x065c9d…c394

3 touches
1 conflict

0x023647ee…afb2

0x34b655…2a6f

2 touches
0 conflicts

0x10f5f4d8…572e

0x34b655…2a6f

2 touches
0 conflicts

0x4778e330…6e63

0x34b655…2a6f

2 touches
0 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

2 touches
0 conflicts

0x664bf99e…0a8c

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

1 conflict on slot 0xf93e2aa15a…4ff3b7

← previous block·next block →recent activity