← previous blocknext block →recent activity

Analyzing

Block #74,655,135

25 transactions · 18 stateful · 2026-05-15 01:44:56 UTC

Parallelism

44/100

Blocked

72%

Avg conflicts / tx

3.64

Longest chain

14 deep

Execution timeline

did this block parallelize well?

view

block #74,655,135  ·  25 txs across 14 waves  ·  depth 14
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

wave w13

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

0x536e2740…61ac

0x3bd359…433a

28 touches
91 conflicts

0xa472d565…9fe4

0x3bd359…433a

28 touches
91 conflicts

0x8fa7a69c…8fd7

0x954bf5…7777

28 touches
91 conflicts

0x00000000…0002

0xa7283d…0ace

28 touches
91 conflicts

0xede0a9e7…0939

0xa7283d…0ace

28 touches
91 conflicts

0xede0a9e7…093a

0xa7283d…0ace

28 touches
91 conflicts

0xede0a9e7…093b

0xa7283d…0ace

28 touches
91 conflicts

0xede0a9e7…093c

0xa7283d…0ace

28 touches
91 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: 0x3bd359c1…15433a

91 conflicts on slot 0x536e2740da…e461ac

← previous block·next block →recent activity