← previous blocknext block →recent activity

Analyzing

Block #74,204,487

16 transactions · 11 stateful · 2026-05-12 23:38:12 UTC

Parallelism

88/100

Blocked

18%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,204,487  ·  16 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xc9a199a6…2ec6

0xd32edf…ff58

3 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x4f0ec8de…6d3d

0x065c9d…c394

2 touches
0 conflicts

0x0ef74796…cd18

0x0a3323…0a3c

2 touches
0 conflicts

0x366be501…7a02

0x0a3323…0a3c

2 touches
0 conflicts

0xb1632c2f…d991

0x0a3323…0a3c

2 touches
0 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

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

1 conflict on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity