← previous blocknext block →recent activity

Analyzing

Block #74,519,950

18 transactions · 11 stateful · 2026-05-14 10:38:34 UTC

Parallelism

89/100

Blocked

9%

Avg conflicts / tx

0.06

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,519,950  ·  18 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

0xa1ccb61a…2306

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0x4d3e58e0…a2d7

0x34b655…2a6f

4 touches
1 conflict

0x1c389468…6b0e

0x34b655…2a6f

4 touches
1 conflict

0x9ba84f5c…a63b

0x065c9d…c394

2 touches
0 conflicts

0x046a928e…0012

0x2a68ba…90c5

2 touches
0 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

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 0xa1ccb61a5a…242306

← previous block·next block →recent activity