← previous blocknext block →recent activity

Analyzing

Block #74,279,253

7 transactions · 6 stateful · 2026-05-13 07:55:16 UTC

Parallelism

57/100

Blocked

33%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,279,253  ·  7 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x7b97d40a…09ed

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

2 touches
0 conflicts

0x1b9e654e…0a08

0x34b655…2a6f

2 touches
0 conflicts

0x29dfc70a…7e09

0x34b655…2a6f

2 touches
0 conflicts

0x2d975111…5f52

0x34b655…2a6f

2 touches
0 conflicts

0x37d49489…9309

0x34b655…2a6f

2 touches
0 conflicts

0x5de96bd3…c60c

0x34b655…2a6f

2 touches
0 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

1 conflict on slot 0x7b97d40a0c…6409ed

← previous block·next block →recent activity