← previous blocknext block →recent activity

Analyzing

Block #73,187,831

27 transactions · 23 stateful · 2026-05-08 06:34:23 UTC

Parallelism

59/100

Blocked

57%

Avg conflicts / tx

1.74

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #73,187,831  ·  27 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

14 touches
21 conflicts

0x046a928e…0012

0x2a68ba…90c5

12 touches
15 conflicts

0xe72225cd…cf01

0xd32edf…ff58

9 touches
10 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0x2a354a63…0515

0x065c9d…c394

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

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: 0x065c9d28…a9c394

21 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity