← previous blocknext block →recent activity

Analyzing

Block #73,297,363

18 transactions · 18 stateful · 2026-05-08 18:43:01 UTC

Parallelism

50/100

Blocked

50%

Avg conflicts / tx

2.06

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,297,363  ·  18 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

0x00000000…003d

0x065c9d…c394

18 touches
36 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xf537eaa0…73c8

0x065c9d…c394

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0xfae1af0c…79cc

0x065c9d…c394

5 touches
3 conflicts

0xa2c1f030…0f44

0x065c9d…c394

5 touches
3 conflicts

0xf0f673fd…37a7

0xaba216…a862

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

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

36 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity