← previous blocknext block →recent activity

Analyzing

Block #74,458,520

33 transactions · 14 stateful · 2026-05-14 03:48:15 UTC

Parallelism

82/100

Blocked

43%

Avg conflicts / tx

0.48

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,458,520  ·  33 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

12 touches
15 conflicts

0x9fc59146…736c

0x34b655…2a6f

6 touches
3 conflicts

0xbc04d98e…a484

0x34b655…2a6f

6 touches
3 conflicts

0xf853eb8e…4027

0x34b655…2a6f

4 touches
1 conflict

0x7170c140…36bc

0x34b655…2a6f

4 touches
1 conflict

0x7cbd466f…1700

0x34b655…2a6f

4 touches
1 conflict

0xe5e7089a…fb91

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

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

← previous block·next block →recent activity