← previous blocknext block →recent activity

Analyzing

Block #75,478,955

32 transactions · 19 stateful · 2026-05-18 21:28:01 UTC

Parallelism

81/100

Blocked

47%

Avg conflicts / tx

0.72

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #75,478,955  ·  32 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x846f2172…fd54

0x0555e3…2b9c

12 touches
15 conflicts

0x46cb45de…a566

0x188d58…ea8e

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x46cb45de…a568

0x188d58…ea8e

6 touches
3 conflicts

0x5086c64a…28ba

0x34b655…2a6f

6 touches
3 conflicts

0xc63eb56f…4bd8

0x34b655…2a6f

4 touches
1 conflict

0xded5ec0c…f0fc

0x34b655…2a6f

4 touches
1 conflict

0xe5e7089a…fb91

0x34b655…2a6f

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: 0x0555e30d…0d2b9c

15 conflicts on slot 0x846f21722e…fdfd54

← previous block·next block →recent activity