← previous blocknext block →recent activity

Analyzing

Block #74,183,178

11 transactions · 7 stateful · 2026-05-12 21:16:30 UTC

Parallelism

82/100

Blocked

14%

Avg conflicts / tx

0.09

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,183,178  ·  11 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

0xeea3f128…72db

0x34b655…2a6f

4 touches
1 conflict

0xdef19d99…c0a9

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x768cffcd…2648

0x34b655…2a6f

4 touches
1 conflict

0x85a88798…f85e

0x34b655…2a6f

4 touches
1 conflict

0x7cee1be1…e770

0x34b655…2a6f

3 touches
1 conflict

0x521a71f4…2a31

0x5afd3e…7620

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 0xeea3f12862…b772db

← previous block·next block →recent activity