← previous blocknext block →recent activity

Analyzing

Block #72,095,084

23 transactions · 16 stateful · 2026-05-03 05:08:44 UTC

Parallelism

78/100

Blocked

38%

Avg conflicts / tx

0.57

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,095,084  ·  23 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xd8384a2a…1e64

0xd32edf…ff58

9 touches
10 conflicts

0xbad68552…e6bf

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x12309510…0ac2

0x000000…012a

2 touches
0 conflicts

0x522477de…2714

0x0555e3…2b9c

2 touches
0 conflicts

0x846f2172…fd54

0x0555e3…2b9c

2 touches
0 conflicts

0x00f7e3b7…e015

0x188d58…ea8e

2 touches
0 conflicts

0x00f7e3b7…e016

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

10 conflicts on slot 0xd8384a2a75…a91e64

← previous block·next block →recent activity