← previous blocknext block →recent activity

Analyzing

Block #75,478,954

42 transactions · 24 stateful · 2026-05-18 21:28:01 UTC

Parallelism

67/100

Blocked

67%

Avg conflicts / tx

2.38

Longest chain

14 deep

Execution timeline

did this block parallelize well?

view

block #75,478,954  ·  42 txs across 14 waves  ·  depth 14
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

wave w13

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

0x585855c2…25ca

0xd32edf…ff58

27 touches
91 conflicts

0x846f2172…fd54

0x0555e3…2b9c

8 touches
6 conflicts

0x00000000…0003

0x094452…0a09

6 touches
3 conflicts

0x00000000…0004

0x094452…0a09

6 touches
3 conflicts

0x62e20208…be65

0x0555e3…2b9c

6 touches
3 conflicts

0x00000000…0000

0x094452…0a09

6 touches
3 conflicts

0x9e223b01…38b2

0x3bd359…433a

6 touches
3 conflicts

0x66de0ce3…337b

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

91 conflicts on slot 0x585855c28f…5625ca

← previous block·next block →recent activity