← previous blocknext block →recent activity

Analyzing

Block #74,899,582

29 transactions · 21 stateful · 2026-05-16 04:56:34 UTC

Parallelism

76/100

Blocked

62%

Avg conflicts / tx

1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,899,582  ·  29 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xea57afd0…4232

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xfe2bac2b…2cec

0x065c9d…c394

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xf3d7a307…4d63

0x065c9d…c394

6 touches
3 conflicts

0x9e2e2fb6…7a04

0xd32edf…ff58

5 touches
3 conflicts

0x4abd98e5…2c0e

0x065c9d…c394

5 touches
3 conflicts

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 0xea57afd097…7f4232

← previous block·next block →recent activity