Block #72,094,845

← previous blocknext block →recent activity

Analyzing

Block #72,094,845

21 transactions · 20 stateful · 2026-05-03 05:07:08 UTC

Parallelism

62/100

Blocked

65%

Avg conflicts / tx

2

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #72,094,845  ·  21 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

14 touches
21 conflicts

0x7f38bfbc…61e3

0x34b655…2a6f

10 touches
10 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xac808a27…82db

0x34b655…2a6f

6 touches
3 conflicts

0xbbad5c01…454e

0x34b655…2a6f

6 touches
3 conflicts

0xc7c4d874…7025

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

21 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity