← previous blocknext block →recent activity

Analyzing

Block #74,040,866

11 transactions · 9 stateful · 2026-05-12 05:29:34 UTC

Parallelism

73/100

Blocked

33%

Avg conflicts / tx

0.36

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,040,866  ·  11 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…0001

0x5c533c…a5a6

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0d711f45…23fc

0x065c9d…c394

2 touches
0 conflicts

0x55801efc…5ad3

0x065c9d…c394

2 touches
0 conflicts

0x572d17ce…aafb

0x065c9d…c394

2 touches
0 conflicts

0x5937dc41…f876

0x065c9d…c394

2 touches
0 conflicts

0xa229aaf9…eb16

0x065c9d…c394

2 touches
0 conflicts

0xbd7e37a9…9eb5

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: 0x5c533c7f…5ba5a6

3 conflicts on slot 0x0000000000…000001

← previous block·next block →recent activity