← previous blocknext block →recent activity

Analyzing

Block #73,043,195

30 transactions · 25 stateful · 2026-05-07 14:32:01 UTC

Parallelism

77/100

Blocked

52%

Avg conflicts / tx

0.93

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,043,195  ·  30 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xce7bfe5e…5e58

0x065c9d…c394

10 touches
10 conflicts

0x251861eb…78fd

0x34b655…2a6f

10 touches
10 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x1b623bb7…e2be

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…001f

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

10 conflicts on slot 0xce7bfe5ef1…205e58

← previous block·next block →recent activity