← previous blocknext block →recent activity

Analyzing

Block #74,654,267

40 transactions · 28 stateful · 2026-05-15 01:39:07 UTC

Parallelism

82/100

Blocked

54%

Avg conflicts / tx

1.1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,654,267  ·  40 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

0x77f99ae4…d4c9

0xd32edf…ff58

11 touches
15 conflicts

0xea02471d…1542

0x34b655…2a6f

10 touches
10 conflicts

0xadac4a86…c2bc

0x34b655…2a6f

10 touches
10 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xfd784183…67bb

0x34b655…2a6f

6 touches
3 conflicts

0x6af306bb…2e81

0x3bd359…433a

6 touches
3 conflicts

0xffe431af…8faa

0x065c9d…c394

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

15 conflicts on slot 0x77f99ae435…b9d4c9

← previous block·next block →recent activity