← previous blocknext block →recent activity

Analyzing

Block #74,439,641

10 transactions · 8 stateful · 2026-05-14 01:42:33 UTC

Parallelism

70/100

Blocked

38%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

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

0xaa147b91…06cb

0x065c9d…c394

4 touches
1 conflict

0x4938d2f5…eee5

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x715487ac…ebc9

0x065c9d…c394

3 touches
1 conflict

0x7fa3d37e…d72f

0x065c9d…c394

3 touches
1 conflict

0x0aaee5aa…0940

0x065c9d…c394

3 touches
1 conflict

0x62c0f4de…477b

0x065c9d…c394

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

1 conflict on slot 0xaa147b9173…7806cb

← previous block·next block →recent activity