← previous blocknext block →recent activity

Analyzing

Block #75,881,126

18 transactions · 18 stateful · 2026-05-20 18:18:32 UTC

Parallelism

67/100

Blocked

50%

Avg conflicts / tx

1.11

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #75,881,126  ·  18 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

0x5086c64a…28ba

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x71a923ba…41eb

0x34b655…2a6f

10 touches
10 conflicts

0x7cee1be1…e770

0x34b655…2a6f

8 touches
6 conflicts

0x892daf6e…48d8

0x065c9d…c394

6 touches
3 conflicts

0xe5e7089a…fb91

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xf3d10975…0d07

0x34b655…2a6f

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: Perpl

15 conflicts on slot 0x5086c64a56…bb28ba

← previous block·next block →recent activity