← previous blocknext block →recent activity

Analyzing

Block #74,918,675

28 transactions · 16 stateful · 2026-05-16 07:03:55 UTC

Parallelism

68/100

Blocked

56%

Avg conflicts / tx

1.11

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,918,675  ·  28 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x1622a697…bfbc

0xd32edf…ff58

15 touches
28 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x729c91b8…9537

0x188d58…ea8e

4 touches
1 conflict

0x729c91b8…9538

0x188d58…ea8e

4 touches
1 conflict

0x00f7e3b7…e015

0x188d58…ea8e

4 touches
1 conflict

0x00f7e3b7…e017

0x188d58…ea8e

4 touches
1 conflict

0x09000000…0001

0x000000…1000

2 touches
0 conflicts

0x4bef88e0…eaca

0x3bd359…433a

2 touches
0 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

28 conflicts on slot 0x1622a69709…21bfbc

← previous block·next block →recent activity