← previous blocknext block →recent activity

Analyzing

Block #72,855,680

27 transactions · 24 stateful · 2026-05-06 17:44:00 UTC

Parallelism

78/100

Blocked

54%

Avg conflicts / tx

0.93

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #72,855,680  ·  27 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

0x3b8ffd61…f3ad

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xce7bfe5e…5e58

0x065c9d…c394

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x3c35979a…975d

0x34b655…2a6f

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: 0x34b6552d…112a6f

6 conflicts on slot 0x3b8ffd6160…92f3ad

← previous block·next block →recent activity