← previous blocknext block →recent activity

Analyzing

Block #73,696,136

35 transactions · 29 stateful · 2026-05-10 15:02:21 UTC

Parallelism

83/100

Blocked

48%

Avg conflicts / tx

0.74

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,696,136  ·  35 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x529acb6a…fcc6

0x065c9d…c394

8 touches
6 conflicts

0xf2438038…5fa7

0x34b655…2a6f

8 touches
6 conflicts

0xb205f2e6…f9fb

0xd32edf…ff58

7 touches
6 conflicts

0x3e733ae4…4598

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0xea02471d…1542

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

6 conflicts on slot 0x529acb6ad1…f0fcc6

← previous block·next block →recent activity