← previous blocknext block →recent activity

Analyzing

Block #75,116,779

13 transactions · 10 stateful · 2026-05-17 05:07:47 UTC

Parallelism

62/100

Blocked

40%

Avg conflicts / tx

0.77

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #75,116,779  ·  13 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x3de7e891…834a

0xd32edf…ff58

7 touches
6 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

6 touches
3 conflicts

0x07bdceeb…b3fa

0x065c9d…c394

5 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x42102e63…8aa5

0x1b6862…e19c

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

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: 0xd32edf66…9fff58

6 conflicts on slot 0x3de7e891bb…b9834a

← previous block·next block →recent activity