← previous blocknext block →recent activity

Analyzing

Block #74,351,913

36 transactions · 22 stateful · 2026-05-13 15:58:33 UTC

Parallelism

86/100

Blocked

41%

Avg conflicts / tx

0.42

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,351,913  ·  36 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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x3f1434d4…1ce1

0x11ed3b…2c96

4 touches
1 conflict

0x00000000…0000

0x2d59fc…cd50

4 touches
1 conflict

0x00000000…0003

0x2d59fc…cd50

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x4f3a6b4a…3819

0x34b655…2a6f

4 touches
1 conflict

0x5d32a251…d929

0x34b655…2a6f

4 touches
1 conflict

0x5ffc25fa…b119

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity