← previous blocknext block →recent activity

Analyzing

Block #75,730,756

18 transactions · 18 stateful · 2026-05-20 01:35:36 UTC

Parallelism

28/100

Blocked

67%

Avg conflicts / tx

4.33

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #75,730,756  ·  18 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

0x1167512f…b162

0x3bd359…433a

26 touches
78 conflicts

0x00000000…0000

0x7214fb…5853

26 touches
78 conflicts

0x00000000…0002

0x7214fb…5853

26 touches
78 conflicts

0x00000000…0003

0x7214fb…5853

26 touches
78 conflicts

0x12711b58…80f3

0x384275…7777

26 touches
78 conflicts

0x30d1accc…cb72

0x384275…7777

2 touches
0 conflicts

0x73a69d96…939d

0x384275…7777

2 touches
0 conflicts

0x8344df32…afa3

0x384275…7777

2 touches
0 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: Wrapped MON (WMON)

78 conflicts on slot 0x1167512f5c…efb162

← previous block·next block →recent activity