← previous blocknext block →recent activity

Analyzing

Block #74,284,284

7 transactions · 6 stateful · 2026-05-13 08:28:44 UTC

Parallelism

57/100

Blocked

50%

Avg conflicts / tx

0.57

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,284,284  ·  7 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x4039af74…60b5

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0xb6157851…b130

0x065c9d…c394

3 touches
1 conflict

0x461f581a…53fa

0x065c9d…c394

3 touches
1 conflict

0x8669d7c1…67ea

0x065c9d…c394

3 touches
1 conflict

0xf1eb35b6…d890

0x065c9d…c394

3 touches
1 conflict

0xb520d8e9…26d2

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

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity