← previous blocknext block →recent activity

Analyzing

Block #75,336,194

32 transactions · 16 stateful · 2026-05-18 05:34:15 UTC

Parallelism

81/100

Blocked

63%

Avg conflicts / tx

0.66

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #75,336,194  ·  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

0x99a21305…dffc

0x2a68ba…90c5

10 touches
10 conflicts

0x443a3e47…f4a4

0x065c9d…c394

8 touches
6 conflicts

0x06e40499…165e

0x1d1325…2305

6 touches
3 conflicts

0x1fff6dcb…b3f4

0xc8689a…ee79

6 touches
3 conflicts

0xfcb7b8b2…ebb3

0x065c9d…c394

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x676f9f01…a8ac

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

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: 0x2a68ba18…8e90c5

10 conflicts on slot 0x99a2130578…57dffc

← previous block·next block →recent activity