Block #72,496,998

← previous blocknext block →recent activity

Analyzing

Block #72,496,998

27 transactions · 19 stateful · 2026-05-05 01:53:16 UTC

Parallelism

74/100

Blocked

53%

Avg conflicts / tx

0.7

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #72,496,998  ·  27 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xd3177fd5…594d

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…001c

0x1b6862…e19c

6 touches
3 conflicts

0xcb45d9d6…cb84

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0xf3981be5…2c47

0x34b655…2a6f

6 touches
3 conflicts

0x08943ea2…ed03

0x754704…b603

6 touches
3 conflicts

0x17e2d2a0…359e

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: 0xd32edf66…9fff58

10 conflicts on slot 0xd3177fd56e…a5594d

← previous block·next block →recent activity