← previous blocknext block →recent activity

Analyzing

Block #72,497,897

10 transactions · 9 stateful · 2026-05-05 01:59:15 UTC

Parallelism

80/100

Blocked

11%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,497,897  ·  10 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xd2fb9655…0ed6

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x7307ddc6…7fc5

0x065c9d…c394

4 touches
1 conflict

0x880484e8…a5cf

0x065c9d…c394

2 touches
0 conflicts

0x976a3cb1…de12

0x065c9d…c394

2 touches
0 conflicts

0xfc26e40d…b28c

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0002

0x7e9d3a…9fda

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

1 conflict on slot 0xd2fb96550b…c20ed6

← previous block·next block →recent activity