← previous blocknext block →recent activity

Analyzing

Block #74,772,313

28 transactions · 21 stateful · 2026-05-15 14:47:32 UTC

Parallelism

86/100

Blocked

43%

Avg conflicts / tx

0.39

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,772,313  ·  28 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

0xb9868b52…c77f

0x34b655…2a6f

6 touches
3 conflicts

0x5138188e…796b

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xfb885840…17c4

0xd32edf…ff58

5 touches
3 conflicts

0x631b4113…baa9

0x34b655…2a6f

4 touches
1 conflict

0x68ae0f54…3c74

0x34b655…2a6f

4 touches
1 conflict

0x84fb2a36…db89

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

3 conflicts on slot 0xb9868b5233…c6c77f

← previous block·next block →recent activity