← previous blocknext block →recent activity

Analyzing

Block #75,478,237

30 transactions · 22 stateful · 2026-05-18 21:23:10 UTC

Parallelism

57/100

Blocked

73%

Avg conflicts / tx

1.87

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #75,478,237  ·  30 txs across 13 waves  ·  depth 13
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

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

0x4b9fb78b…64f6

0xd32edf…ff58

17 touches
36 conflicts

0x17606ba6…1b6e

0x754704…b603

10 touches
10 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x17a7f697…dcb1

0x1b6862…e19c

8 touches
6 conflicts

0x46cb45de…a566

0x188d58…ea8e

8 touches
6 conflicts

0x00000000…0000

0xca50b9…1d03

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

36 conflicts on slot 0x4b9fb78bb0…d064f6

← previous block·next block →recent activity