← previous blocknext block →recent activity

Analyzing

Block #73,651,645

20 transactions · 19 stateful · 2026-05-10 10:02:13 UTC

Parallelism

65/100

Blocked

58%

Avg conflicts / tx

2

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,651,645  ·  20 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

0x00000000…003d

0x065c9d…c394

14 touches
21 conflicts

0x046a928e…0012

0x2a68ba…90c5

12 touches
15 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0x0ac31945…2c72

0x065c9d…c394

8 touches
6 conflicts

0x529acb6a…fcc6

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0xfc2b514e…7dcb

0x065c9d…c394

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

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

21 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity