← previous blocknext block →recent activity

Analyzing

Block #74,555,897

30 transactions · 21 stateful · 2026-05-14 14:40:58 UTC

Parallelism

87/100

Blocked

48%

Avg conflicts / tx

0.6

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,555,897  ·  30 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

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xb2471674…39bd

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x0d0b2509…074d

0x3bd359…433a

6 touches
3 conflicts

0xe6455d1f…1029

0x754704…b603

6 touches
3 conflicts

0x8a35acfb…d1a3

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1a6

0x8d66a4…3095

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