← previous blocknext block →recent activity

Analyzing

Block #74,289,838

9 transactions · 8 stateful · 2026-05-13 09:05:42 UTC

Parallelism

78/100

Blocked

13%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,289,838  ·  9 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

0x6d369fa6…295c

0x34b655…2a6f

4 touches
1 conflict

0x7b7bcac3…8fbf

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

2 touches
0 conflicts

0x1eb0fab5…3517

0x34b655…2a6f

2 touches
0 conflicts

0x5aed1bd2…7afa

0x34b655…2a6f

2 touches
0 conflicts

0xac2a0273…7212

0x34b655…2a6f

2 touches
0 conflicts

0xbb12db23…857e

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 0x6d369fa644…b5295c

← previous block·next block →recent activity