← previous blocknext block →recent activity

Analyzing

Block #75,533,500

7 transactions · 7 stateful · 2026-05-19 03:40:18 UTC

Parallelism

71/100

Blocked

29%

Avg conflicts / tx

0.29

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,533,500  ·  7 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

0x5086c64a…28ba

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x99a21305…dffc

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x5f77d607…2c84

0x065c9d…c394

2 touches
0 conflicts

0x10abefc9…c9bc

0x1d1325…2305

2 touches
0 conflicts

0x10d80fee…dbda

0x1d1325…2305

2 touches
0 conflicts

0x3484c9df…bfd5

0x1d1325…2305

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 0x5086c64a56…bb28ba

← previous block·next block →recent activity