← previous blocknext block →recent activity

Analyzing

Block #74,422,900

16 transactions · 15 stateful · 2026-05-13 23:51:02 UTC

Parallelism

56/100

Blocked

40%

Avg conflicts / tx

1.19

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,422,900  ·  16 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xadac4a86…c2bc

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0xd40bddc1…773c

0x34b655…2a6f

8 touches
6 conflicts

0xd7a175ca…f443

0x34b655…2a6f

8 touches
6 conflicts

0x80a6e76c…277f

0x34b655…2a6f

6 touches
3 conflicts

0xef17b8cd…9511

0x34b655…2a6f

6 touches
3 conflicts

0x4d3e58e0…a2d7

0x34b655…2a6f

5 touches
3 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

15 conflicts on slot 0xadac4a860c…a3c2bc

← previous block·next block →recent activity