← previous blocknext block →recent activity

Analyzing

Block #74,336,477

16 transactions · 11 stateful · 2026-05-13 14:15:57 UTC

Parallelism

81/100

Blocked

18%

Avg conflicts / tx

0.13

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,336,477  ·  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

0x04f0e47d…cb70

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xf3981be5…2c47

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x847d5b61…c544

0x065c9d…c394

2 touches
0 conflicts

0xd282e3e8…a645

0x065c9d…c394

2 touches
0 conflicts

0xfb083229…0138

0x2a68ba…90c5

2 touches
0 conflicts

0x4a6a2a1a…c177

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

1 conflict on slot 0x04f0e47d2b…a8cb70

← previous block·next block →recent activity