← previous blocknext block →recent activity

Analyzing

Block #74,237,720

8 transactions · 7 stateful · 2026-05-13 03:19:12 UTC

Parallelism

63/100

Blocked

29%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,237,720  ·  8 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

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0x0520da1d…c88e

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x768cffcd…2648

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xcf3283ba…c9fa

0x065c9d…c394

2 touches
0 conflicts

0xd2b8323f…f51a

0x065c9d…c394

2 touches
0 conflicts

0xdcfea322…6ee8

0x065c9d…c394

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 0xea02471df2…601542

← previous block·next block →recent activity