← previous blocknext block →recent activity

Analyzing

Block #74,730,741

37 transactions · 15 stateful · 2026-05-15 10:09:34 UTC

Parallelism

89/100

Blocked

47%

Avg conflicts / tx

0.35

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,730,741  ·  37 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

0x801a6e57…d85c

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xfe2bac2b…2cec

0x065c9d…c394

6 touches
3 conflicts

0x7d9ded6f…4a79

0x065c9d…c394

5 touches
3 conflicts

0x67dd4c17…af5d

0x065c9d…c394

5 touches
3 conflicts

0x00000000…0019

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0029

0x1b6862…e19c

4 touches
1 conflict

0x8b41ec8f…c2d4

0x1b6862…e19c

4 touches
1 conflict

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

6 conflicts on slot 0x801a6e5726…c1d85c

← previous block·next block →recent activity