← previous blocknext block →recent activity

Analyzing

Block #74,762,892

23 transactions · 19 stateful · 2026-05-15 13:44:26 UTC

Parallelism

65/100

Blocked

42%

Avg conflicts / tx

0.87

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,762,892  ·  23 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

0xf853eb8e…4027

0x34b655…2a6f

8 touches
6 conflicts

0x388e001a…7e04

0x34b655…2a6f

6 touches
3 conflicts

0x37cfaf01…4a46

0x34b655…2a6f

6 touches
3 conflicts

0x7170c140…36bc

0x34b655…2a6f

6 touches
3 conflicts

0x75f6889e…7f1e

0x34b655…2a6f

6 touches
3 conflicts

0x1674d3d4…275f

0x34b655…2a6f

6 touches
3 conflicts

0x5138188e…796b

0x34b655…2a6f

6 touches
3 conflicts

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