← previous blocknext block →recent activity

Analyzing

Block #74,344,470

8 transactions · 7 stateful · 2026-05-13 15:09:07 UTC

Parallelism

63/100

Blocked

43%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,344,470  ·  8 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

0x62d080e9…4a7c

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x399cd013…b14f

0x23ae8c…7777

4 touches
1 conflict

0x35019383…fc7d

0x34b655…2a6f

4 touches
1 conflict

0x55b6a001…1e7a

0x34b655…2a6f

4 touches
1 conflict

0xb4b3c404…f0aa

0x3bd359…433a

4 touches
1 conflict

0x7cbd466f…1700

0x34b655…2a6f

4 touches
1 conflict

0xaa0d0542…d8ec

0x34b655…2a6f

4 touches
1 conflict

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 0x62d080e928…5a4a7c

← previous block·next block →recent activity