← previous blocknext block →recent activity

Analyzing

Block #74,377,421

30 transactions · 28 stateful · 2026-05-13 18:48:19 UTC

Parallelism

50/100

Blocked

64%

Avg conflicts / tx

3.63

Longest chain

15 deep

Execution timeline

did this block parallelize well?

view

block #74,377,421  ·  30 txs across 15 waves  ·  depth 15
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

wave w14

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

30 touches
105 conflicts

0xa472d565…9fe4

0x3bd359…433a

30 touches
105 conflicts

0xd4303785…bf32

0xa7283d…0ace

30 touches
105 conflicts

0xd4303785…bf31

0xa7283d…0ace

30 touches
105 conflicts

0xd4303785…bf30

0xa7283d…0ace

30 touches
105 conflicts

0x8fa7a69c…8fd7

0xad5005…7777

30 touches
105 conflicts

0xd4303785…bf2f

0xa7283d…0ace

30 touches
105 conflicts

0x00000000…0002

0xa7283d…0ace

30 touches
105 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

105 conflicts on slot 0x536e2740da…e461ac

← previous block·next block →recent activity