Block #73,211,553

← previous blocknext block →recent activity

Analyzing

Block #73,211,553

18 transactions · 17 stateful · 2026-05-08 09:12:11 UTC

Parallelism

50/100

Blocked

53%

Avg conflicts / tx

2.17

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,211,553  ·  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

0x7f189cf6…afab

0x065c9d…c394

16 touches
28 conflicts

0x00000000…003d

0x065c9d…c394

14 touches
21 conflicts

0x046a928e…0012

0x2a68ba…90c5

12 touches
15 conflicts

0xce7bfe5e…5e58

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x9df7cc9b…5513

0x065c9d…c394

3 touches
1 conflict

0xbd28f9de…953e

0x065c9d…c394

3 touches
1 conflict

0x5b571ba0…f13a

0x368ee5…7ca4

2 touches
0 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

28 conflicts on slot 0x7f189cf621…beafab

← previous block·next block →recent activity