← previous blocknext block →recent activity

Analyzing

Block #74,597,477

20 transactions · 19 stateful · 2026-05-14 19:19:59 UTC

Parallelism

35/100

Blocked

63%

Avg conflicts / tx

3.9

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #74,597,477  ·  20 txs across 13 waves  ·  depth 13
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

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

0x8fa7a69c…8fd7

0x17a62e…7777

26 touches
78 conflicts

0x536e2740…61ac

0x3bd359…433a

26 touches
78 conflicts

0xa472d565…9fe4

0x3bd359…433a

26 touches
78 conflicts

0x00000000…0002

0xa7283d…0ace

26 touches
78 conflicts

0xcba59bf3…8d1d

0xa7283d…0ace

26 touches
78 conflicts

0xcba59bf3…8d1e

0xa7283d…0ace

26 touches
78 conflicts

0xcba59bf3…8d1f

0xa7283d…0ace

26 touches
78 conflicts

0xcba59bf3…8d20

0xa7283d…0ace

26 touches
78 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: 0x17a62efc…027777

78 conflicts on slot 0x8fa7a69c55…388fd7

← previous block·next block →recent activity