← previous blocknext block →recent activity

Analyzing

Block #74,646,994

32 transactions · 21 stateful · 2026-05-15 00:50:35 UTC

Parallelism

75/100

Blocked

48%

Avg conflicts / tx

1.06

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,646,994  ·  32 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x438eab26…0522

0xd32edf…ff58

15 touches
28 conflicts

0x00000000…0004

0x094452…0a09

6 touches
3 conflicts

0x9e223b01…38b2

0x3bd359…433a

6 touches
3 conflicts

0x00000000…0003

0x094452…0a09

6 touches
3 conflicts

0x62e20208…be65

0x0555e3…2b9c

6 touches
3 conflicts

0x846f2172…fd54

0x0555e3…2b9c

6 touches
3 conflicts

0x00000000…0000

0x094452…0a09

6 touches
3 conflicts

0x46cb45de…a568

0x188d58…ea8e

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

28 conflicts on slot 0x438eab2649…1a0522

← previous block·next block →recent activity