← previous blocknext block →recent activity

Analyzing

Block #74,698,227

12 transactions · 11 stateful · 2026-05-15 06:32:19 UTC

Parallelism

83/100

Blocked

18%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,698,227  ·  12 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

0xafc586fc…6243

0x065c9d…c394

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0xfd8f2e44…461f

0x065c9d…c394

3 touches
1 conflict

0xd6df65c7…4d04

0x065c9d…c394

3 touches
1 conflict

0x229ea86d…b9cc

0x065c9d…c394

2 touches
0 conflicts

0x47b807a2…3307

0x065c9d…c394

2 touches
0 conflicts

0x4ee55a29…4b5f

0x065c9d…c394

2 touches
0 conflicts

0x81ba238f…5fb4

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 0xafc586fc00…136243

← previous block·next block →recent activity