← previous blocknext block →recent activity

Analyzing

Block #74,229,248

13 transactions · 12 stateful · 2026-05-13 02:22:51 UTC

Parallelism

77/100

Blocked

42%

Avg conflicts / tx

0.54

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,229,248  ·  13 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

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x768cffcd…2648

0x34b655…2a6f

4 touches
1 conflict

0xcf3283ba…c9fa

0x065c9d…c394

4 touches
1 conflict

0xf823e97f…2ee6

0x065c9d…c394

4 touches
1 conflict

0x59a54ff4…d21b

0x34b655…2a6f

2 touches
0 conflicts

0x7b7bcac3…8fbf

0x34b655…2a6f

2 touches
0 conflicts

0xcdfad956…e7de

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: 0x2a68ba18…8e90c5

3 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity