← previous blocknext block →recent activity

Analyzing

Block #74,353,226

18 transactions · 13 stateful · 2026-05-13 16:07:17 UTC

Parallelism

78/100

Blocked

23%

Avg conflicts / tx

0.28

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,353,226  ·  18 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

0x801a6e57…d85c

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xfc6205fa…4d80

0x34b655…2a6f

4 touches
1 conflict

0x7cee1be1…e770

0x34b655…2a6f

4 touches
1 conflict

0xfb083229…0138

0x2a68ba…90c5

2 touches
0 conflicts

0x536e2740…61ac

0x3bd359…433a

2 touches
0 conflicts

0xa472d565…9fe4

0x3bd359…433a

2 touches
0 conflicts

0x8f98c21d…9ac3

0x4082a0…7777

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 0x801a6e5726…c1d85c

← previous block·next block →recent activity