← previous blocknext block →recent activity

Analyzing

Block #74,402,933

20 transactions · 14 stateful · 2026-05-13 21:38:12 UTC

Parallelism

65/100

Blocked

57%

Avg conflicts / tx

1.2

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,402,933  ·  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

0x0824c484…d962

0x3bd359…433a

4 touches
1 conflict

0x8afb5cb3…b803

0x3bd359…433a

2 touches
1 conflict

0xf735e90f…54dc

0x3bd359…433a

2 touches
1 conflict

0x09000000…0001

0x000000…1000

2 touches
0 conflicts

0xdbadf6b0…43b2

0x33176b…e078

2 touches
0 conflicts

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x00000000…000b

0x14ef59…ca7e

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