← previous blocknext block →recent activity

Analyzing

Block #75,116,783

13 transactions · 11 stateful · 2026-05-17 05:07:49 UTC

Parallelism

85/100

Blocked

18%

Avg conflicts / tx

0.15

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,116,783  ·  13 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

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0xba38536d…2b7d

0x065c9d…c394

4 touches
1 conflict

0x73912233…4583

0x1b6862…e19c

4 touches
1 conflict

0xfc60e1f0…6d9f

0x065c9d…c394

3 touches
1 conflict

0x672ee0ff…a8c5

0xd32edf…ff58

3 touches
1 conflict

0x132712a5…8f52

0x065c9d…c394

2 touches
0 conflicts

0x1e57a3ae…f174

0x065c9d…c394

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: 0x1b68626d…2de19c

1 conflict on slot 0x0000000000…000013

← previous block·next block →recent activity