← previous blocknext block →recent activity

Analyzing

Block #74,352,299

10 transactions · 9 stateful · 2026-05-13 16:01:07 UTC

Parallelism

80/100

Blocked

22%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,352,299  ·  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

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xab60dc09…85e4

0x34b655…2a6f

4 touches
1 conflict

0xd06f7aba…49a0

0xd32edf…ff58

3 touches
1 conflict

0x09106a95…1467

0x33176b…e078

2 touches
0 conflicts

0x09fe2003…e416

0x34b655…2a6f

2 touches
0 conflicts

0x0de7749d…5bef

0x34b655…2a6f

2 touches
0 conflicts

0x2c539d94…b63a

0x34b655…2a6f

2 touches
0 conflicts

0x2d129439…f341

0x34b655…2a6f

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity