← previous blocknext block →recent activity

Analyzing

Block #74,782,848

16 transactions · 15 stateful · 2026-05-15 15:57:57 UTC

Parallelism

75/100

Blocked

40%

Avg conflicts / tx

0.63

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,782,848  ·  16 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

0x856a8137…05ca

0xd32edf…ff58

7 touches
6 conflicts

0x84fb2a36…db89

0x34b655…2a6f

6 touches
3 conflicts

0x2965e2d6…5800

0x34b655…2a6f

6 touches
3 conflicts

0xc4901160…05ad

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xf3d10975…0d07

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad04

0x34b655…2a6f

4 touches
1 conflict

0xe5e7089a…fb91

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

6 conflicts on slot 0x856a81377c…bc05ca

← previous block·next block →recent activity