← previous blocknext block →recent activity

Analyzing

Block #73,043,130

35 transactions · 23 stateful · 2026-05-07 14:31:35 UTC

Parallelism

83/100

Blocked

48%

Avg conflicts / tx

0.66

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,043,130  ·  35 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x60f7fbaf…bd58

0x34b655…2a6f

12 touches
15 conflicts

0x01e7b865…6e6f

0x188d58…ea8e

6 touches
3 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x8a35acfb…d1ab

0x8d66a4…3095

6 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0x15c9b5bf…f732

0x34b655…2a6f

4 touches
1 conflict

0x664bf99e…0a8c

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: 0x34b6552d…112a6f

15 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity