← previous blocknext block →recent activity

Analyzing

Block #74,609,353

14 transactions · 11 stateful · 2026-05-14 20:39:44 UTC

Parallelism

86/100

Blocked

27%

Avg conflicts / tx

0.21

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,609,353  ·  14 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

0xadac4a86…c2bc

0x34b655…2a6f

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0xbeccd910…7888

0x065c9d…c394

3 touches
1 conflict

0x3e1f7818…2fc8

0x34b655…2a6f

2 touches
0 conflicts

0x4b90cfff…b2b3

0x34b655…2a6f

2 touches
0 conflicts

0x543da691…8f99

0x34b655…2a6f

2 touches
0 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

2 touches
0 conflicts

0x9a291a56…9a9c

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

1 conflict on slot 0xadac4a860c…a3c2bc

← previous block·next block →recent activity