← previous blocknext block →recent activity

Analyzing

Block #74,353,762

16 transactions · 10 stateful · 2026-05-13 16:10:51 UTC

Parallelism

88/100

Blocked

10%

Avg conflicts / tx

0.06

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,353,762  ·  16 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

0xef17b8cd…9511

0x34b655…2a6f

4 touches
1 conflict

0x4d3e58e0…a2d7

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x62e20208…be65

0x0555e3…2b9c

2 touches
0 conflicts

0x846f2172…fd54

0x0555e3…2b9c

2 touches
0 conflicts

0x8edd456e…c7e3

0x0555e3…2b9c

2 touches
0 conflicts

0x969f2d28…4fa2

0x0555e3…2b9c

2 touches
0 conflicts

0x9bad8822…a28c

0x0555e3…2b9c

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: 0x34b6552d…112a6f

1 conflict on slot 0xef17b8cd5c…709511

← previous block·next block →recent activity