← previous blocknext block →recent activity

Analyzing

Block #75,205,536

9 transactions · 7 stateful · 2026-05-17 15:00:20 UTC

Parallelism

78/100

Blocked

14%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,205,536  ·  9 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x8fbde2b3…9b8f

0x34b655…2a6f

4 touches
1 conflict

0x0c6a56ad…d8a8

0x2ab50b…5c41

2 touches
0 conflicts

0x1035ed1e…3885

0x2ab50b…5c41

2 touches
0 conflicts

0x132711dc…851a

0x2ab50b…5c41

2 touches
0 conflicts

0x15a8b5e6…0296

0x2ab50b…5c41

2 touches
0 conflicts

0x1bbd2e06…5e6f

0x2ab50b…5c41

2 touches
0 conflicts

0x21a005d7…c779

0x2ab50b…5c41

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

1 conflict on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity