← previous blocknext block →recent activity

Analyzing

Block #73,338,529

25 transactions · 16 stateful · 2026-05-08 23:16:55 UTC

Parallelism

48/100

Blocked

75%

Avg conflicts / tx

3.12

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #73,338,529  ·  25 txs across 13 waves  ·  depth 13
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

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

0x7f7ec799…fe30

0xd32edf…ff58

25 touches
78 conflicts

0x00000000…0004

0xd5b70d…615b

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x00000000…0000

0xd5b70d…615b

4 touches
1 conflict

0x00000000…0003

0xd5b70d…615b

4 touches
1 conflict

0x12309510…0ac2

0x000000…012a

4 touches
1 conflict

0x18aed20c…48f3

0x000000…012a

4 touches
1 conflict

0x33018431…8f5c

0x188d58…ea8e

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: 0xd32edf66…9fff58

78 conflicts on slot 0x7f7ec7993d…25fe30

← previous block·next block →recent activity