← previous blocknext block →recent activity

Analyzing

Block #74,486,993

10 transactions · 10 stateful · 2026-05-14 06:57:40 UTC

Parallelism

60/100

Blocked

40%

Avg conflicts / tx

0.7

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,486,993  ·  10 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

0xbc04d98e…a484

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x6dd62d2b…f17e

0x34b655…2a6f

6 touches
3 conflicts

0x85a88798…f85e

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0002

0xfdc9ea…8789

4 touches
1 conflict

0x44ad89ba…cf83

0x23c26b…7777

4 touches
1 conflict

0x81a7ba4d…8c4b

0x23c26b…7777

4 touches
1 conflict

0xf3d10975…0d07

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 0xbc04d98e5a…d5a484

← previous block·next block →recent activity