← previous blocknext block →recent activity

Analyzing

Block #73,981,270

17 transactions · 16 stateful · 2026-05-11 22:51:17 UTC

Parallelism

53/100

Blocked

69%

Avg conflicts / tx

2.65

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,981,270  ·  17 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x00000000…003d

0x065c9d…c394

14 touches
21 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

12 touches
15 conflicts

0xf537eaa0…73c8

0x065c9d…c394

10 touches
10 conflicts

0x6f08361d…bda6

0x065c9d…c394

10 touches
10 conflicts

0x046a928e…0012

0x2a68ba…90c5

10 touches
10 conflicts

0x92474f11…3fca

0x065c9d…c394

3 touches
1 conflict

0x1de7c78f…2cad

0x065c9d…c394

3 touches
1 conflict

0x7680ee17…7234

0x065c9d…c394

3 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

21 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity