← previous blocknext block →recent activity

Analyzing

Block #74,419,096

7 transactions · 7 stateful · 2026-05-13 23:25:45 UTC

Parallelism

71/100

Blocked

14%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,419,096  ·  7 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

0x62d080e9…4a7c

0x34b655…2a6f

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

2 touches
0 conflicts

0x220f4f84…15f8

0x34b655…2a6f

2 touches
0 conflicts

0x2cf96c0a…538a

0x34b655…2a6f

2 touches
0 conflicts

0x5138188e…796b

0x34b655…2a6f

2 touches
0 conflicts

0x5675c293…17d9

0x34b655…2a6f

2 touches
0 conflicts

0x908d4442…2c4b

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