← previous blocknext block →recent activity

Analyzing

Block #75,205,467

10 transactions · 9 stateful · 2026-05-17 14:59:54 UTC

Parallelism

60/100

Blocked

33%

Avg conflicts / tx

0.6

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #75,205,467  ·  10 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0x0d0b2509…074d

0x3bd359…433a

4 touches
1 conflict

0xe6455d1f…1029

0x754704…b603

4 touches
1 conflict

0xc3c8642a…7da5

0x2a68ba…90c5

4 touches
1 conflict

0x8e80434a…a96d

0x0555e3…2b9c

2 touches
0 conflicts

0x3efcf3cb…7f07

0x065c9d…c394

2 touches
0 conflicts

0x486b5846…7696

0x065c9d…c394

2 touches
0 conflicts

0x46cb45de…a566

0x188d58…ea8e

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: 0x754704bc…afb603

6 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity