← previous blocknext block →recent activity

Analyzing

Block #72,497,889

27 transactions · 24 stateful · 2026-05-05 01:59:12 UTC

Parallelism

70/100

Blocked

54%

Avg conflicts / tx

1.48

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #72,497,889  ·  27 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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…0002

0x7e9d3a…9fda

16 touches
28 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0xf3981be5…2c47

0x34b655…2a6f

8 touches
6 conflicts

0x2877f440…c2c8

0x34b655…2a6f

6 touches
3 conflicts

0x3702b140…97ea

0x34b655…2a6f

6 touches
3 conflicts

0x414e9446…4b59

0x34b655…2a6f

6 touches
3 conflicts

0x4ee6f153…3ef4

0x34b655…2a6f

6 touches
3 conflicts

0x7501f58e…a219

0x34b655…2a6f

6 touches
3 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: 0x7e9d3a8a…4f9fda

28 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity