← previous blocknext block →recent activity

Analyzing

Block #75,468,389

17 transactions · 13 stateful · 2026-05-18 20:17:40 UTC

Parallelism

65/100

Blocked

54%

Avg conflicts / tx

1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #75,468,389  ·  17 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

0x9cc778a3…2452

0x34b655…2a6f

12 touches
15 conflicts

0xea02471d…1542

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x5086c64a…28ba

0x34b655…2a6f

8 touches
6 conflicts

0xfd784183…67bb

0x34b655…2a6f

8 touches
6 conflicts

0x408e66bb…3d6b

0x34b655…2a6f

6 touches
3 conflicts

0x0eac6378…36f4

0x34b655…2a6f

6 touches
3 conflicts

0x21d22421…0b7a

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: 0x34b6552d…112a6f

15 conflicts on slot 0x9cc778a3d6…5d2452

← previous block·next block →recent activity