← previous blocknext block →recent activity

Analyzing

Block #74,764,048

39 transactions · 25 stateful · 2026-05-15 13:52:07 UTC

Parallelism

82/100

Blocked

56%

Avg conflicts / tx

0.87

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,764,048  ·  39 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

0xa9253d6c…a4b3

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…0002

0xab3526…fa38

8 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x56a919c4…ab49

0xee8c0e…1242

4 touches
1 conflict

0x18aed20c…48f3

0x000000…012a

4 touches
1 conflict

0x443a3e47…f4a4

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0xd98b3c10…67b8

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: 0xd32edf66…9fff58

21 conflicts on slot 0xa9253d6c44…a3a4b3

← previous block·next block →recent activity