← previous blocknext block →recent activity

Analyzing

Block #74,010,355

10 transactions · 7 stateful · 2026-05-12 02:07:01 UTC

Parallelism

80/100

Blocked

14%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,010,355  ·  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

0x9ea57326…329f

0x34b655…2a6f

4 touches
1 conflict

0xc4bbcfff…cbc5

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x25b2d98f…8cc4

0x065c9d…c394

2 touches
0 conflicts

0x3a52ea41…74b5

0x065c9d…c394

2 touches
0 conflicts

0x626b5698…1b38

0x065c9d…c394

2 touches
0 conflicts

0x6f08361d…bda6

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 0x9ea57326ca…60329f

← previous block·next block →recent activity