← previous blocknext block →recent activity

Analyzing

Block #74,183,293

10 transactions · 10 stateful · 2026-05-12 21:17:16 UTC

Parallelism

70/100

Blocked

20%

Avg conflicts / tx

0.3

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

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

0xa52a1bf1…9d20

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x0146366a…02dd

0x065c9d…c394

3 touches
1 conflict

0x9cc6a61f…bbd7

0x065c9d…c394

3 touches
1 conflict

0x530511d4…21d3

0x065c9d…c394

2 touches
0 conflicts

0x7f988543…2860

0x065c9d…c394

2 touches
0 conflicts

0xdd3866be…921d

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 0xa52a1bf1d9…719d20

← previous block·next block →recent activity