← previous blocknext block →recent activity

Analyzing

Block #74,359,631

14 transactions · 12 stateful · 2026-05-13 16:49:54 UTC

Parallelism

64/100

Blocked

33%

Avg conflicts / tx

0.71

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,359,631  ·  14 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x8c49c85c…ee96

0x34b655…2a6f

10 touches
10 conflicts

0x5a9c2dc3…43ab

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xf3d10975…0d07

0x34b655…2a6f

4 touches
1 conflict

0x3347cbe5…846c

0x34b655…2a6f

4 touches
1 conflict

0x41d3bfa5…523e

0x34b655…2a6f

4 touches
1 conflict

0x9b36f19f…fa5a

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: 0x34b6552d…112a6f

10 conflicts on slot 0x8c49c85c3e…afee96

← previous block·next block →recent activity