← previous blocknext block →recent activity

Analyzing

Block #74,240,784

10 transactions · 8 stateful · 2026-05-13 03:39:33 UTC

Parallelism

80/100

Blocked

25%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,240,784  ·  10 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

0xcf3283ba…c9fa

0x065c9d…c394

4 touches
1 conflict

0x4af638b5…fdfd

0x34b655…2a6f

4 touches
1 conflict

0x768cffcd…2648

0x34b655…2a6f

4 touches
1 conflict

0x85a88798…f85e

0x34b655…2a6f

4 touches
1 conflict

0x151c06b2…09e4

0x065c9d…c394

2 touches
0 conflicts

0x473b639f…8943

0x065c9d…c394

2 touches
0 conflicts

0x4d6ba879…ee1a

0x065c9d…c394

2 touches
0 conflicts

0xa59f413a…f77a

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: 0x065c9d28…a9c394

1 conflict on slot 0xcf3283bab2…c3c9fa

← previous block·next block →recent activity