← previous blocknext block →recent activity

Analyzing

Block #74,417,053

9 transactions · 8 stateful · 2026-05-13 23:12:10 UTC

Parallelism

67/100

Blocked

25%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,417,053  ·  9 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

0x4d3e58e0…a2d7

0x34b655…2a6f

4 touches
1 conflict

0xef17b8cd…9511

0x34b655…2a6f

4 touches
1 conflict

0x18aed20c…48f3

0x000000…012a

2 touches
0 conflicts

0x4245e4e8…096e

0x000000…012a

2 touches
0 conflicts

0x5fad6fee…7714

0x34b655…2a6f

2 touches
0 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

2 touches
0 conflicts

0x664bf99e…0a8c

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity