← previous blocknext block →recent activity

Analyzing

Block #74,781,807

34 transactions · 24 stateful · 2026-05-15 15:50:57 UTC

Parallelism

76/100

Blocked

46%

Avg conflicts / tx

0.71

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,781,807  ·  34 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xf853eb8e…4027

0x34b655…2a6f

6 touches
3 conflicts

0x388e001a…7e04

0x34b655…2a6f

6 touches
3 conflicts

0x57de3828…3fbb

0x34b655…2a6f

4 touches
1 conflict

0xd49762c9…1359

0x34b655…2a6f

4 touches
1 conflict

0xedb848fe…6534

0x34b655…2a6f

4 touches
1 conflict

0x1686502b…a1d2

0x3bd359…433a

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity