← previous blocknext block →recent activity

Analyzing

Block #74,281,630

15 transactions · 10 stateful · 2026-05-13 08:11:05 UTC

Parallelism

80/100

Blocked

20%

Avg conflicts / tx

0.2

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,281,630  ·  15 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

6 touches
3 conflicts

0xc3e03394…7165

0x065c9d…c394

4 touches
1 conflict

0x002ec3b5…39cc

0x065c9d…c394

3 touches
1 conflict

0x5a23814e…b484

0x065c9d…c394

2 touches
0 conflicts

0x6d2e32c3…b5b9

0x065c9d…c394

2 touches
0 conflicts

0x750707a7…69f0

0x065c9d…c394

2 touches
0 conflicts

0x99c17569…c417

0x065c9d…c394

2 touches
0 conflicts

0xa487b942…3ee3

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity