← previous blocknext block →recent activity

Analyzing

Block #73,483,241

17 transactions · 15 stateful · 2026-05-09 15:19:47 UTC

Parallelism

47/100

Blocked

67%

Avg conflicts / tx

2.29

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,483,241  ·  17 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

0xf2f76ab3…623e

0x2a68ba…90c5

12 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

12 touches
15 conflicts

0x046a928e…0012

0x2a68ba…90c5

12 touches
15 conflicts

0xf537eaa0…73c8

0x065c9d…c394

8 touches
6 conflicts

0x2451a390…72f3

0x065c9d…c394

4 touches
1 conflict

0x77e91ad9…d732

0x065c9d…c394

4 touches
1 conflict

0x8a994ffc…f644

0x065c9d…c394

4 touches
1 conflict

0xe51ad8b0…023d

0x065c9d…c394

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: 0x2a68ba18…8e90c5

15 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity