← previous blocknext block →recent activity

Analyzing

Block #73,976,020

13 transactions · 10 stateful · 2026-05-11 22:16:01 UTC

Parallelism

69/100

Blocked

40%

Avg conflicts / tx

0.54

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,976,020  ·  13 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

0xf537eaa0…73c8

0x065c9d…c394

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x73333fea…bf03

0x065c9d…c394

3 touches
1 conflict

0x30276c1c…47b4

0x2a68ba…90c5

2 touches
0 conflicts

0x765c236f…ff45

0x2a68ba…90c5

2 touches
0 conflicts

0x2e2214a9…fe0d

0x5d823e…89c6

2 touches
0 conflicts

0x3e4b8d9f…b8a7

0x5d823e…89c6

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: 0x065c9d28…a9c394

6 conflicts on slot 0xf537eaa0c6…3873c8

← previous block·next block →recent activity