← previous blocknext block →recent activity

Analyzing

Block #76,042,674

20 transactions · 17 stateful · 2026-05-21 12:13:53 UTC

Parallelism

65/100

Blocked

53%

Avg conflicts / tx

1.2

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #76,042,674  ·  20 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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…0002

0xab3526…fa38

14 touches
21 conflicts

0xfcb7b8b2…ebb3

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xbe7dd2f3…cb2a

0x065c9d…c394

4 touches
1 conflict

0x676f9f01…a8ac

0x34b655…2a6f

4 touches
1 conflict

0x8fa0889f…0346

0x34b655…2a6f

4 touches
1 conflict

0x66000db1…da21

0x065c9d…c394

2 touches
0 conflicts

0x09000000…0007

0x000000…1000

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: 0xab35264b…1cfa38

21 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity