← previous blocknext block →recent activity

Analyzing

Block #74,765,321

30 transactions · 20 stateful · 2026-05-15 14:00:40 UTC

Parallelism

80/100

Blocked

55%

Avg conflicts / tx

0.8

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,765,321  ·  30 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xe5b03940…d880

0xd32edf…ff58

11 touches
15 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x849f3e33…c095

0x34b655…2a6f

4 touches
1 conflict

0xecd3dd4f…0f84

0x34b655…2a6f

4 touches
1 conflict

0xfa09be5a…1e79

0x34b655…2a6f

4 touches
1 conflict

0xfac43f12…b842

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

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: 0xd32edf66…9fff58

15 conflicts on slot 0xe5b03940db…ced880

← previous block·next block →recent activity