← previous blocknext block →recent activity

Analyzing

Block #74,369,568

15 transactions · 10 stateful · 2026-05-13 17:56:01 UTC

Parallelism

87/100

Blocked

30%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,369,568  ·  15 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

0x1b9e654e…0a08

0x34b655…2a6f

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x908d4442…2c4b

0x34b655…2a6f

4 touches
1 conflict

0xba85143e…a3e5

0x34b655…2a6f

4 touches
1 conflict

0x62d080e9…4a7c

0x34b655…2a6f

4 touches
1 conflict

0xefb1e776…e79c

0x065c9d…c394

3 touches
1 conflict

0x7c1ccbd1…92bb

0x34b655…2a6f

2 touches
0 conflicts

0x83ce31c8…22ac

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 0x1b9e654ec8…aa0a08

← previous block·next block →recent activity