← previous blocknext block →recent activity

Analyzing

Block #74,763,035

26 transactions · 23 stateful · 2026-05-15 13:45:24 UTC

Parallelism

65/100

Blocked

61%

Avg conflicts / tx

1.81

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,763,035  ·  26 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x44bb8417…1fb5

0xd32edf…ff58

17 touches
36 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x676f9f01…a8ac

0x34b655…2a6f

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0xba7ac612…4822

0x065c9d…c394

5 touches
3 conflicts

0xf34802b3…9f0f

0x1b6862…e19c

4 touches
1 conflict

0x56a919c4…ab49

0xe7cd86…c82d

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

36 conflicts on slot 0x44bb841739…fb1fb5

← previous block·next block →recent activity