← previous blocknext block →recent activity

Analyzing

Block #74,625,918

13 transactions · 9 stateful · 2026-05-14 22:30:11 UTC

Parallelism

85/100

Blocked

11%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,625,918  ·  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

0x967123a1…901f

0x34b655…2a6f

4 touches
1 conflict

0xd895ee0b…d301

0x34b655…2a6f

4 touches
1 conflict

0x0c4acf96…dbbf

0x34b655…2a6f

3 touches
1 conflict

0xd7c2e23a…d1ea

0x34b655…2a6f

3 touches
1 conflict

0x140b9466…1bc2

0x065c9d…c394

2 touches
0 conflicts

0x48d53c7f…2e47

0x065c9d…c394

2 touches
0 conflicts

0x563fd741…2b55

0x065c9d…c394

2 touches
0 conflicts

0x5c8c6ab6…dc36

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 0x967123a133…1c901f

← previous block·next block →recent activity