← previous blocknext block →recent activity

Analyzing

Block #74,763,024

16 transactions · 15 stateful · 2026-05-15 13:45:19 UTC

Parallelism

88/100

Blocked

20%

Avg conflicts / tx

0.19

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,763,024  ·  16 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

0x22e0cc1d…ad04

0x34b655…2a6f

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0xe7c3e49e…2ecd

0x065c9d…c394

3 touches
1 conflict

0x749437cf…2fc1

0x2880ab…7b43

2 touches
0 conflicts

0x10814d14…cdda

0x34b655…2a6f

2 touches
0 conflicts

0x1991586b…f893

0x34b655…2a6f

2 touches
0 conflicts

0x37179c06…3c8c

0x34b655…2a6f

2 touches
0 conflicts

0x46e2bb67…d8b3

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 0x22e0cc1d4a…90ad04

← previous block·next block →recent activity