← previous blocknext block →recent activity

Analyzing

Block #73,202,181

11 transactions · 9 stateful · 2026-05-08 08:09:52 UTC

Parallelism

73/100

Blocked

22%

Avg conflicts / tx

0.27

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,202,181  ·  11 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x7f189cf6…afab

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x494299ab…2b59

0x065c9d…c394

2 touches
0 conflicts

0xba007659…7579

0x065c9d…c394

2 touches
0 conflicts

0xc275b4c3…07d7

0x065c9d…c394

2 touches
0 conflicts

0xc3c0f47e…7666

0x065c9d…c394

2 touches
0 conflicts

0xda01dab3…47d5

0x065c9d…c394

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: 0x065c9d28…a9c394

3 conflicts on slot 0x7f189cf621…beafab

← previous block·next block →recent activity