← previous blocknext block →recent activity

Analyzing

Block #73,043,157

31 transactions · 24 stateful · 2026-05-07 14:31:46 UTC

Parallelism

71/100

Blocked

54%

Avg conflicts / tx

1

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,043,157  ·  31 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

12 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0xc1ceff4b…04a0

0x3bd359…433a

6 touches
3 conflicts

0xd19f9d56…9330

0x3bd359…433a

6 touches
3 conflicts

0xc13c1093…9a9d

0x754704…b603

6 touches
3 conflicts

0x56a919c4…ab49

0xee8c0e…1242

6 touches
3 conflicts

0xf0426f7b…d105

0xd32edf…ff58

5 touches
3 conflicts

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

15 conflicts on slot 0xce7bfe5ef1…205e58

← previous block·next block →recent activity