← previous blocknext block →recent activity

Analyzing

Block #74,462,712

10 transactions · 10 stateful · 2026-05-14 04:16:10 UTC

Parallelism

60/100

Blocked

30%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,462,712  ·  10 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

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xf3981be5…2c47

0x34b655…2a6f

4 touches
1 conflict

0x63d7ebf0…3dd9

0x34b655…2a6f

4 touches
1 conflict

0x4a320f8b…2baf

0x34b655…2a6f

2 touches
0 conflicts

0x8d13ecc1…980f

0x34b655…2a6f

2 touches
0 conflicts

0x97d5efed…1aa4

0x34b655…2a6f

2 touches
0 conflicts

0xc08384da…ecb7

0x34b655…2a6f

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

3 conflicts on slot 0x1c38946843…a16b0e

← previous block·next block →recent activity