← previous blocknext block →recent activity

Analyzing

Block #74,501,530

14 transactions · 12 stateful · 2026-05-14 08:34:28 UTC

Parallelism

71/100

Blocked

33%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,501,530  ·  14 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

0x84fb2a36…db89

0x34b655…2a6f

6 touches
3 conflicts

0x445aaad5…6c0f

0x699abc…6a3b

4 touches
1 conflict

0x93429156…835e

0x699abc…6a3b

4 touches
1 conflict

0x335a161d…fe7f

0x000000…012a

4 touches
1 conflict

0x5aed1bd2…7afa

0x34b655…2a6f

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0xb2471674…39bd

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