← previous blocknext block →recent activity

Analyzing

Block #74,204,521

13 transactions · 9 stateful · 2026-05-12 23:38:25 UTC

Parallelism

85/100

Blocked

22%

Avg conflicts / tx

0.15

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,204,521  ·  13 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

0x1728ed63…499c

0xea1b8e…c5ec

4 touches
1 conflict

0x00bac013…a28c

0xfd44b3…00d1

4 touches
1 conflict

0x9a266c50…c366

0xd32edf…ff58

3 touches
1 conflict

0x58af9303…a978

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0013

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0015

0x1b6862…e19c

2 touches
0 conflicts

0xdb95e18e…c73d

0x1b6862…e19c

2 touches
0 conflicts

0x30276c1c…47b4

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: 0xea1b8e4a…8fc5ec

1 conflict on slot 0x1728ed6317…a9499c

← previous block·next block →recent activity