← previous blocknext block →recent activity

Analyzing

Block #73,478,379

27 transactions · 17 stateful · 2026-05-09 14:47:28 UTC

Parallelism

70/100

Blocked

53%

Avg conflicts / tx

1.11

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,478,379  ·  27 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x4e7d0d59…99f1

0xd32edf…ff58

15 touches
28 conflicts

0x18aed20c…48f3

0x000000…012a

4 touches
1 conflict

0x7c403af1…31b1

0x3bd359…433a

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x00000000…0000

0xd5b70d…615b

4 touches
1 conflict

0x00000000…0002

0xd5b70d…615b

4 touches
1 conflict

0x01e7b865…6e6d

0x188d58…ea8e

4 touches
1 conflict

0x00000000…0004

0xd5b70d…615b

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

28 conflicts on slot 0x4e7d0d59ec…7f99f1

← previous block·next block →recent activity