← previous blocknext block →recent activity

Analyzing

Block #75,079,337

8 transactions · 6 stateful · 2026-05-17 00:57:47 UTC

Parallelism

75/100

Blocked

17%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,079,337  ·  8 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

0x765c236f…ff45

0x2a68ba…90c5

4 touches
1 conflict

0xd152721c…a27d

0x065c9d…c394

3 touches
1 conflict

0x846f2172…fd54

0x0555e3…2b9c

2 touches
0 conflicts

0x969f2d28…4fa2

0x0555e3…2b9c

2 touches
0 conflicts

0x9bad8822…a28c

0x0555e3…2b9c

2 touches
0 conflicts

0xa24d15eb…cc92

0x0555e3…2b9c

2 touches
0 conflicts

0xbda8437d…1a61

0x0555e3…2b9c

2 touches
0 conflicts

0xe64f78af…51a7

0x0555e3…2b9c

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: 0x2a68ba18…8e90c5

1 conflict on slot 0x765c236f2d…b5ff45

← previous block·next block →recent activity