← previous blocknext block →recent activity

Analyzing

Block #74,763,021

15 transactions · 11 stateful · 2026-05-15 13:45:18 UTC

Parallelism

60/100

Blocked

55%

Avg conflicts / tx

1.13

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,763,021  ·  15 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

0xb795088a…d360

0xd32edf…ff58

11 touches
15 conflicts

0x388e001a…7e04

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x56a919c4…ab49

0x01bff4…1071

2 touches
0 conflicts

0x78eb0de5…1db2

0x01bff4…1071

2 touches
0 conflicts

0x40c0484d…8192

0x188d58…ea8e

2 touches
0 conflicts

0x40c0484d…8194

0x188d58…ea8e

2 touches
0 conflicts

0x703b861a…cbe3

0x188d58…ea8e

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 0xb795088a6a…4ad360

← previous block·next block →recent activity