← previous blocknext block →recent activity

Analyzing

Block #75,514,167

25 transactions · 18 stateful · 2026-05-19 01:29:40 UTC

Parallelism

72/100

Blocked

44%

Avg conflicts / tx

0.92

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #75,514,167  ·  25 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x44ad89ba…cf83

0x0cc9b2…7777

14 touches
21 conflicts

0x99a3a7c1…1e2b

0x0cc9b2…7777

14 touches
21 conflicts

0xa10c86f8…4b74

0x3bd359…433a

14 touches
21 conflicts

0xa472d565…9fe4

0x3bd359…433a

14 touches
21 conflicts

0x00000000…0000

0x019883…2a9a

14 touches
21 conflicts

0x00000000…0002

0x019883…2a9a

14 touches
21 conflicts

0xf3d10975…0d07

0x34b655…2a6f

4 touches
1 conflict

0x5086c64a…28ba

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: MONI (MONI)

21 conflicts on slot 0x44ad89ba62…49cf83

← previous block·next block →recent activity