← previous blocknext block →recent activity

Analyzing

Block #74,644,021

21 transactions · 14 stateful · 2026-05-15 00:30:47 UTC

Parallelism

71/100

Blocked

43%

Avg conflicts / tx

0.76

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,644,021  ·  21 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xe3160860…7986

0xd32edf…ff58

11 touches
15 conflicts

0xe8adf936…34b0

0x188d58…ea8e

4 touches
1 conflict

0x703b861a…cbe3

0x188d58…ea8e

4 touches
1 conflict

0x56a919c4…ab49

0x01bff4…1071

4 touches
1 conflict

0x56a919c4…ab49

0xe7cd86…c82d

4 touches
1 conflict

0x78eb0de5…1db2

0x01bff4…1071

2 touches
0 conflicts

0x703b861a…cbe4

0x188d58…ea8e

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

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

15 conflicts on slot 0xe3160860dc…a07986

← previous block·next block →recent activity