← previous blocknext block →recent activity

Analyzing

Block #74,396,460

20 transactions · 19 stateful · 2026-05-13 20:55:06 UTC

Parallelism

80/100

Blocked

47%

Avg conflicts / tx

0.75

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,396,460  ·  20 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x1c389468…6b0e

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0002

0xab3526…fa38

8 touches
6 conflicts

0xfe3d37ee…6e67

0x34b655…2a6f

6 touches
3 conflicts

0xb0146d76…55f4

0x34b655…2a6f

6 touches
3 conflicts

0xb245fe36…d765

0x34b655…2a6f

6 touches
3 conflicts

0x59a54ff4…d21b

0x34b655…2a6f

4 touches
1 conflict

0x5c0e5bb8…4f6e

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

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: 0x34b6552d…112a6f

6 conflicts on slot 0x1c38946843…a16b0e

← previous block·next block →recent activity