← previous blocknext block →recent activity

Analyzing

Block #73,270,615

30 transactions · 23 stateful · 2026-05-08 15:45:04 UTC

Parallelism

67/100

Blocked

52%

Avg conflicts / tx

1.63

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #73,270,615  ·  30 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x7a852bad…b5b2

0xd32edf…ff58

19 touches
45 conflicts

0x00000000…0002

0x63e48b…53f2

4 touches
1 conflict

0x00000000…0004

0x63e48b…53f2

4 touches
1 conflict

0x9a555477…19a8

0x754704…b603

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0x4dd1db39…a995

0x188d58…ea8e

4 touches
1 conflict

0x1eff1251…5bfd

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

45 conflicts on slot 0x7a852badd7…17b5b2

← previous block·next block →recent activity