← previous blocknext block →recent activity

Analyzing

Block #74,765,002

17 transactions · 14 stateful · 2026-05-15 13:58:32 UTC

Parallelism

76/100

Blocked

29%

Avg conflicts / tx

0.41

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,765,002  ·  17 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x676f9f01…a8ac

0x34b655…2a6f

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x37674bd8…8f35

0x34b655…2a6f

4 touches
1 conflict

0x55836904…a6fe

0x34b655…2a6f

4 touches
1 conflict

0xad2bb81f…4d6b

0x34b655…2a6f

4 touches
1 conflict

0x08d31c28…d50f

0x34b655…2a6f

4 touches
1 conflict

0x1c1b5ec9…43f6

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

6 conflicts on slot 0x676f9f01ee…dea8ac

← previous block·next block →recent activity