← previous blocknext block →recent activity

Analyzing

Block #73,955,695

19 transactions · 17 stateful · 2026-05-11 20:00:23 UTC

Parallelism

63/100

Blocked

65%

Avg conflicts / tx

1.68

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,955,695  ·  19 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

0x6f08361d…bda6

0x065c9d…c394

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x046a928e…0012

0x2a68ba…90c5

10 touches
10 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

10 touches
10 conflicts

0xf537eaa0…73c8

0x065c9d…c394

6 touches
5 conflicts

0xa81ee49b…9e10

0xd32edf…ff58

5 touches
3 conflicts

0xcb45d9d6…cb82

0x1b6862…e19c

4 touches
1 conflict

0x22e295f5…1bef

0x065c9d…c394

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 0x6f08361da9…89bda6

← previous block·next block →recent activity