← previous blocknext block →recent activity

Analyzing

Block #74,284,192

10 transactions · 9 stateful · 2026-05-13 08:28:08 UTC

Parallelism

70/100

Blocked

44%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,284,192  ·  10 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xdf1c279f…4014

0x065c9d…c394

4 touches
1 conflict

0x00000000…00c9

0x34b655…2a6f

4 touches
1 conflict

0x30276c1c…47b4

0x2a68ba…90c5

3 touches
1 conflict

0x46cb45de…a566

0x188d58…ea8e

2 touches
0 conflicts

0x06cdf7f0…fbe6

0x3bd359…433a

2 touches
0 conflicts

0xb9eb1318…ce53

0x3bd359…433a

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

3 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity