← previous blocknext block →recent activity

Analyzing

Block #74,762,833

30 transactions · 23 stateful · 2026-05-15 13:44:02 UTC

Parallelism

67/100

Blocked

52%

Avg conflicts / tx

1.3

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,762,833  ·  30 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x6abc44f6…ccf4

0xd32edf…ff58

15 touches
28 conflicts

0x443a3e47…f4a4

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

4 touches
2 conflicts

0xfcb7b8b2…ebb3

0x065c9d…c394

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

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: 0xd32edf66…9fff58

28 conflicts on slot 0x6abc44f6a3…15ccf4

← previous block·next block →recent activity