← previous blocknext block →recent activity

Analyzing

Block #74,352,186

16 transactions · 11 stateful · 2026-05-13 16:00:21 UTC

Parallelism

81/100

Blocked

27%

Avg conflicts / tx

0.25

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,352,186  ·  16 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0xd602bd87…38da

0x065c9d…c394

2 touches
0 conflicts

0x729c91b8…9537

0x188d58…ea8e

2 touches
0 conflicts

0x729c91b8…9538

0x188d58…ea8e

2 touches
0 conflicts

0xfb083229…0138

0x2a68ba…90c5

2 touches
0 conflicts

0x0be70560…c7e7

0x2ab50b…5c41

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity