← previous blocknext block →recent activity

Analyzing

Block #72,974,400

9 transactions · 8 stateful · 2026-05-07 06:54:05 UTC

Parallelism

56/100

Blocked

38%

Avg conflicts / tx

0.56

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,974,400  ·  9 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x7f189cf6…afab

0x065c9d…c394

4 touches
1 conflict

0xd8836e4f…8065

0x065c9d…c394

4 touches
1 conflict

0x65d719f3…223c

0x065c9d…c394

2 touches
0 conflicts

0x865f5e6e…c9a4

0x065c9d…c394

2 touches
0 conflicts

0xa9dbe66e…85ac

0x065c9d…c394

2 touches
0 conflicts

0xac254637…3880

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: 0x2a68ba18…8e90c5

3 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity