← previous blocknext block →recent activity

Analyzing

Block #72,856,184

36 transactions · 29 stateful · 2026-05-06 17:47:20 UTC

Parallelism

58/100

Blocked

62%

Avg conflicts / tx

2.08

Longest chain

15 deep

Execution timeline

did this block parallelize well?

view

block #72,856,184  ·  36 txs across 15 waves  ·  depth 15
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

wave w13

wave w14

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

0x61bfca0a…6bd8

0xd32edf…ff58

19 touches
45 conflicts

0x00000000…003d

0x065c9d…c394

12 touches
15 conflicts

0xce7bfe5e…5e58

0x065c9d…c394

12 touches
15 conflicts

0x7f189cf6…afab

0x065c9d…c394

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xcb45d9d6…cb84

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

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

45 conflicts on slot 0x61bfca0a88…016bd8

← previous block·next block →recent activity