← previous blocknext block →recent activity

Analyzing

Block #74,650,812

15 transactions · 13 stateful · 2026-05-15 01:15:57 UTC

Parallelism

80/100

Blocked

15%

Avg conflicts / tx

0.2

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

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

4 touches
1 conflict

0xffe431af…8faa

0x065c9d…c394

4 touches
1 conflict

0xf5f6478c…f487

0xd32edf…ff58

3 touches
1 conflict

0x222a9f55…14e6

0x065c9d…c394

2 touches
0 conflicts

0x2748d049…ccfd

0x065c9d…c394

2 touches
0 conflicts

0x6364bde1…1038

0x065c9d…c394

2 touches
0 conflicts

0x6d474dd4…3f2e

0x065c9d…c394

2 touches
0 conflicts

0x75f2f0cd…a6df

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