← previous blocknext block →recent activity

Analyzing

Block #71,746,832

28 transactions · 23 stateful · 2026-05-01 14:30:18 UTC

Parallelism

64/100

Blocked

48%

Avg conflicts / tx

1.75

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #71,746,832  ·  28 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x1079b814…7ae8

0xd32edf…ff58

19 touches
45 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

6 touches
3 conflicts

0xf2d0c7ba…bd2f

0x065c9d…c394

5 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x77e5e0a4…2e6d

0x065c9d…c394

4 touches
1 conflict

0x88e57395…b951

0x065c9d…c394

4 touches
1 conflict

0x00000000…002d

0x1b6862…e19c

4 touches
1 conflict

0x35801c67…bcc3

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 0x1079b81479…4c7ae8

← previous block·next block →recent activity