← previous blocknext block →recent activity

Analyzing

Block #72,855,723

26 transactions · 21 stateful · 2026-05-06 17:44:17 UTC

Parallelism

77/100

Blocked

48%

Avg conflicts / tx

0.81

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #72,855,723  ·  26 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

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x2905340c…dbc6

0x34b655…2a6f

6 touches
3 conflicts

0xce7bfe5e…5e58

0x065c9d…c394

6 touches
3 conflicts

0x8043784c…1ef5

0x065c9d…c394

4 touches
1 conflict

0x8806fb9c…c686

0x065c9d…c394

4 touches
1 conflict

0xb0cda67a…34f2

0x065c9d…c394

4 touches
1 conflict

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

10 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity