← previous blocknext block →recent activity

Analyzing

Block #75,084,897

11 transactions · 7 stateful · 2026-05-17 01:35:01 UTC

Parallelism

73/100

Blocked

29%

Avg conflicts / tx

0.27

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,084,897  ·  11 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0x41d3bfa5…523e

0x34b655…2a6f

4 touches
1 conflict

0x96aa7e47…f584

0x34b655…2a6f

4 touches
1 conflict

0x1c1a981e…f3da

0xea1b8e…c5ec

2 touches
0 conflicts

0x3572bd92…dd29

0xea1b8e…c5ec

2 touches
0 conflicts

0x3694f0c3…6b8c

0xea1b8e…c5ec

2 touches
0 conflicts

0x36f6824c…700a

0xea1b8e…c5ec

2 touches
0 conflicts

0x3a328f13…995e

0xea1b8e…c5ec

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity