← previous blocknext block →recent activity

Analyzing

Block #74,416,818

20 transactions · 16 stateful · 2026-05-13 23:10:37 UTC

Parallelism

80/100

Blocked

25%

Avg conflicts / tx

0.35

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,416,818  ·  20 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0xfa9f4f8d…ddc5

0x34b655…2a6f

4 touches
1 conflict

0x335a161d…fe7f

0x000000…012a

4 touches
1 conflict

0x3552a26a…ce1f

0x34b655…2a6f

4 touches
1 conflict

0x379adc5a…3b1b

0x699abc…6a3b

4 touches
1 conflict

0xc00479bf…cc66

0x699abc…6a3b

4 touches
1 conflict

0x62d080e9…4a7c

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity