Block #73,334,172

← previous blocknext block →recent activity

Analyzing

Block #73,334,172

17 transactions · 16 stateful · 2026-05-08 22:47:58 UTC

Parallelism

59/100

Blocked

44%

Avg conflicts / tx

1.18

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,334,172  ·  17 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

0xf537eaa0…73c8

0x065c9d…c394

12 touches
15 conflicts

0x046a928e…0012

0x2a68ba…90c5

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x6f08361d…bda6

0x065c9d…c394

4 touches
1 conflict

0x5e6b48f5…fa40

0x065c9d…c394

2 touches
0 conflicts

0x9a0cfc8b…9a55

0x065c9d…c394

2 touches
0 conflicts

0xa1ccc58e…7d88

0x065c9d…c394

2 touches
0 conflicts

0xeb1af794…8bb0

0x065c9d…c394

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

15 conflicts on slot 0xf537eaa0c6…3873c8

← previous block·next block →recent activity