← previous blocknext block →recent activity

Analyzing

Block #74,353,790

39 transactions · 24 stateful · 2026-05-13 16:11:02 UTC

Parallelism

67/100

Blocked

63%

Avg conflicts / tx

1.92

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #74,353,790  ·  39 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

0xa3416173…5de2

0xd32edf…ff58

23 touches
66 conflicts

0x41755291…977f

0x065c9d…c394

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0029

0x1b6862…e19c

6 touches
3 conflicts

0x21d8e673…067a

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0019

0x1b6862…e19c

6 touches
3 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: 0xd32edf66…9fff58

66 conflicts on slot 0xa3416173af…145de2

← previous block·next block →recent activity