← previous blocknext block →recent activity

Analyzing

Block #74,382,911

16 transactions · 10 stateful · 2026-05-13 19:24:53 UTC

Parallelism

81/100

Blocked

30%

Avg conflicts / tx

0.25

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,382,911  ·  16 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xb10b3eb2…e35f

0x065c9d…c394

4 touches
1 conflict

0x30276c1c…47b4

0x2a68ba…90c5

4 touches
1 conflict

0xc03a03cd…fbcf

0x34b655…2a6f

4 touches
1 conflict

0xd40bddc1…773c

0x34b655…2a6f

4 touches
1 conflict

0x4dd1db39…a994

0x188d58…ea8e

2 touches
0 conflicts

0x264c6e4e…cbb6

0x3bd359…433a

2 touches
0 conflicts

0xf8127de7…d5ec

0x3bd359…433a

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity